Upload, find and publish media
Media files use private storage and separate editable/public metadata. An uploaded file is not automatically public. The library paginates 24 assets at a time.
How to use it
- Open Media and upload an allowed image or file within the current size and plan limits.
- Add a useful title, alternative text and description where appropriate, then save metadata.
- Use search, numbered pages and grid/list views to find files. Open an asset to inspect its details independently of the current page.
- Use All files to search the whole environment, Unfiled for files without a folder, or open a folder to browse its direct files and subfolders. Folder, search and page are kept in the URL. Uploads go into the currently open folder; uploads from All files or entry fields start Unfiled.
- With media-update permission, open New folder to create a folder or subfolder. Manage folder lets you rename it or remove it when it contains no files, pending uploads, cleanup records or subfolders. Names are unique within each parent, up to 80 characters; organization is bounded to 200 folders per environment and five levels.
- Select files with checkboxes or Select this page, choose a destination and click Move files. Selection covers the current page only and clears when folder, search, page or environment changes. Alternatively drag a file handle onto a visible folder; use Escape to cancel. For touch or keyboard use, the checkbox and destination controls provide the same move operation.
- Folder moves apply immediately and are all-or-nothing. They preserve original bytes, asset IDs, references, published metadata and delivery paths. Save metadata edits before moving. If a selected file changed elsewhere, clear the selection, review and select again. Moves advance the editing version, so other open media editors or pinned release reviews may need refreshing.
- Publish it before using it in published content. Use Where used before unpublishing or deleting it.
Good practice
- Write alternative text for the image's meaning in context; retain licensing/provenance separately when your process requires it.
Avoid
- Do not use the private studio asset URL as a permanent public URL or assume a file extension proves content safety.
- Folders organize the Studio library; they are not access-control boundaries or storage directories. They do not affect REST/GraphQL/RPC payloads. Import/export and environment promotion preserve their existing media behavior and do not transfer folder organization in this version. Full database backups include it.
Choose a focal point and responsive crops
Smart images derive bounded rendition recipes from the immutable original. The focal point keeps the subject visible across supported aspect ratios.
How to use it
- Inspect an eligible image and position its focal point using the editor controls.
- Review the available responsive crop previews and adjust the focal point if a face or subject is cut off.
- Save and publish the metadata. Use the returned rendition URLs in the website's responsive image markup.
- Verify the actual website at narrow and wide widths; draft crop edits remain separate from the published recipe.
Good practice
- Keep the original as the source of truth and choose appropriate sizes for each rendered slot.
Avoid
- Do not overwrite original bytes, fabricate arbitrary transformation URLs or assume a CMS crop is used when the website still requests the original.
Handle removals and delivery failures
Asset deletion, unpublication and plan capacity are distinct operations. References can prevent removal when public content still depends on an asset.
How to use it
- Inspect Where used and replace references before removing a shared asset.
- Unpublish when it should be offline but retained for editing; delete only when it is no longer needed.
- If delivery or rendering fails, check publication state, storage connectivity, credential scope and rendition version rather than repeatedly uploading duplicates.
Good practice
- Keep storage backups coordinated with database backups so restored rows still have their original files.
Avoid
- A database-only backup cannot restore missing original object bytes.