Media that knows where it is used
The media library is where every image, video, audio file and document in a project lives. Each asset carries its own alt text, caption, tags and focal point, plus a usage list naming the pages and fields that point at it.
Your stack. Your rules. Everyone moves faster.
What the media library does
-
Filter down to one asset
Eight type chips carry counts, from image to audio. Smart filters find unused files and missing alt text.
-
See where an asset is used
A usage list names every page and field using it. Each row is a working link into that place.
-
Crop and focal point
Set the focal point once, on the asset itself. Every card, the inspector and the picker read it.
-
Replace without hunting
Swap the file and every reference repoints to it. The usage count guards the swap before it runs.
-
Alt text and transcripts
Alt text, captions and tags live on the asset. Transcripts for video and audio ship in the markdown output.
-
BetterCMS is headless by default and serves content over an API to any framework. It also ships a page builder, so teams that want one tool can stay in it.
-
The Migrator API maps an existing schema onto BetterCMS collections and brings entries and assets with it. WordPress, Contentful, and Sanity are covered.
-
Yes. Free includes one locale, Starter two and Pro five, and an extra locale is $8 a month per website. Translate inside the editor and publish each locale on its own schedule from the same content model.
-
There is no cap. Build models in the schema builder with your own fields, relationships, and validation rules, and change them without a migration.
-
The media library stores and organizes every asset. Images are resized, compressed, and served from a CDN, so you upload once and use the file anywhere.
-
Yes. Editors work side by side with live cursors, comments, and field locking, and every version is kept for your plan history window, 7 days on Free, 90 on Starter and 365 on Pro, so you can roll back to an earlier draft.
-
Set custom roles down to the field. Decide who can edit, who has to approve, and who is allowed to publish, then apply the same rules to your agents.
-
Content is encrypted at rest and in transit, backed up automatically, and every change is written to an audit log you can read.