Upload and organise files
Supported formats, limits shown in product and folders.
Upload and organise files
VELORYZ Studio · Media, assets and content management Audience: Content teams, asset owners and implementers Guide type: Practical Studio operations guide
Purpose
Upload and organise files should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Supported formats, limits shown in product and folders.
This guide covers supported formats, limits shown in product and folders. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
The Studio source includes protected media management with validation and storage integration. Upload permissions and storage availability depend on the deployed backend configuration; a customer-facing media library is not promised.
Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.
Before you begin
- An original or properly licensed asset and its usage permission
- Desired crop, focal area, dimensions, compression target and alt text
- A safe filename and replacement/retention plan
- A short list of measurable success criteria specifically for upload and organise files.
- A recovery plan if the proposed change creates a regression.
Recommended procedure
- Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
- Define the specific work item for Upload and organise files: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
- Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
- Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
- After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.
Topic-specific operating procedure
These steps apply to Upload and organise files. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.
- Choose supported image/video formats and confirm file-size limits in the current admin implementation.
- Use descriptive filenames and metadata; reject unsupported or spoofed MIME types server-side.
- Upload through authenticated media controls, then verify the returned URL and actual display.
- Avoid replacing a published asset until there is a tested fallback.
Evidence to retain
- The original input or situation, and a clear before/after comparison.
- The reviewed version, responsible owner and acceptance record.
- Any limitation, follow-up decision, or safely reversible workaround.
Configuration and decision points
- Use the approved owner/admin media workflow for supported files.
- Choose appropriate resolution and responsive variants without upscaling low-quality artwork.
- Record license/source information for third-party items and confirm brand usage rights.
- Preview the real media URL and mobile crop before publishing pages.
When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.
Verification checklist
- No placeholder or watermarked imagery is represented as original work.
- Images have meaningful alternatives when informational; decorative art is hidden from assistive technology.
- Assets load on narrow connections and avoid excessive layout shifts.
- Private files and credentials are not exposed through public URLs.
Also confirm that the result addresses the original objective: Supported formats, limits shown in product and folders.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.
Troubleshooting and recovery
- If upload fails, confirm file type, size and storage configuration.
- If media is broken after publishing, restore a previously verified asset or fallback.
- If rights are uncertain, remove the asset until permission is documented.
When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.
Related reading
- [Media library overview](/docs/studio/media/overview/)
- [Image optimisation and focal points](/docs/studio/media/image-optimisation/)
- [Video and audio assets](/docs/studio/media/video-audio/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/create/](/create/)
- [/docs/overview/](/docs/overview/)
Operational note
This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.
