Media

Studio stores Media metadata in D1 and managed file bytes in its MEDIA_BUCKET R2 binding. A Media record can also reference an external HTTP(S) file. Collections organize records without moving their underlying objects.

Storage and Delivery

Resource	Contains
Studio D1	Media identity, metadata, collections, and storage references
Studio R2	Managed uploads and imported objects
External host	Files registered by their existing public URLs
Media address in Site Settings	The public origin used to resolve managed references during export

Uploading a file and setting its public delivery address are separate steps. An ordinary R2 custom domain uses Standard media URLs. ZeroPress media domain expects a delivery service that implements ZeroPress image variants; an R2 custom domain alone does not provide those variants.

Use an origin such as https://media.example.com for the Media address. An object key imported/2024/06/photo.jpg then resolves beneath that origin. Changing the address changes generated references, not the object keys in R2. Prepare and publish new data for the public site to use the changed address.

Editing and Insertion

Media management includes metadata, collections, uploads, and image tools. Selecting a Media record in a Post or Page inserts its content representation; the body preview lets you inspect the result before saving or publishing. Public delivery still depends on the saved Media settings and available files.

Authors can select existing Media while editing their own Posts. Uploads and Media management require additional permissions; see Roles & Capabilities.

Imported WordPress Media

WXR contains attachment metadata rather than image bytes. Keep existing storage retains dependencies on the original public URLs. Use Studio R2 registers imported object references and rewrites matching body references, but does not copy or verify the files in R2.

Copy WordPress uploads separately and preserve the expected object keys. Follow WordPress Migration for the source prefix, R2 copy, and delivery setup.

Deletion and Backup

Deleting Media metadata and deleting managed objects are distinct parts of the workflow. External HTTP(S) files are not physically deleted by Studio. Clear Content and Reset Studio record managed keys for cleanup and retain failed cleanup work for retry. Uninstall removes the Studio schema but leaves R2 objects in place.

A D1 backup contains Media metadata, not R2 bytes. Preserve the corresponding objects separately when making a recoverable site backup. See Backups & Restore.