Capa
Contact salesGet started
Changelog

What’s new in Capa.

Everything we ship, newest first, in plain words. Each entry says what changed and where to find it.

New

The new Capa is live

A new API with dated versions, visual editing on your own site, an Assistant that builds models and drafts content, an MCP server for your coding agents, and access scoped to exactly what each person needs.

  • The Content API: REST under /api/ and GraphQL at /api/graphql, dated by a Capa-Version header and read from cdn.capacms.com.
  • Visual Editing and Live Preview: your own site beside the editor. Click text on the page to edit the field behind it.
  • The Assistant: ask for a model or a batch of content. It shows a plan, works inside your access, and nothing goes live until someone publishes.
  • The MCP server: @capacms/mcp gives Claude Code, Cursor and Codex your schema and content, read with your key.
  • Teams & Roles: scope each person to the projects, models and actions they need, publishing included.
  • SDK & CLI: @capacms/sdk with typed reads, codegen, persisted queries and the editing overlay.
  • Scoped API keys with expiry, allowed origins, and rotation with a grace window.
  • And this site, with a page for every product.
Tour the platformStart free

Showing all 24 changes.

September 2026

  • Admin

Every project has its own address

The project you are in is now part of every admin link, so a link you share opens the same page in the same project for anyone in it.

What changed
  • Open two projects in two tabs and work in both. Switching project in one tab no longer changes the other.
  • Links name models and entries in words: /content/articles/my-first-post-ad0d5a8a instead of two long ids. Renaming an entry keeps its link working.
  • Change the project's address in Settings, Project. Links from before this change still work.
  • Publishing

One place to publish what is waiting

The new Publish page lists every entry, across every model, whose saved changes are not live yet. Review them, then publish, schedule or discard them together.

What changed
  • Each row says whether the entry is new or edited, which fields changed, who changed them and when, and the page it lives on. The sidebar shows how many are waiting.
  • Click a row to see its changes: removed words struck through and added words highlighted, and the before and after for relations and media. Open the entry or preview its page from there.
  • Tick entries, or every entry that matches your filters, and publish them now or schedule them for one time. Tonight at 9, tomorrow at 9 and next Monday at 9 are one click away.
  • Discard puts entries back to their published version. The discarded draft stays in the entry's history.
  • The Scheduled tab shows what goes out next, grouped by when, with Publish now, Reschedule and Cancel on each batch and each entry.
  • Editor
  • Preview

Preview on mobile, tablet and desktop

The preview now shows your page the way each device really lays it out, and the editor beside it is easier to work in.

What changed
  • Pick Mobile, Tablet or Desktop. The page renders at that device's real width and shrinks to fit, with the size shown as a percentage you can click to see it at full size. Turn Mobile and Tablet sideways with one button.
  • The preview shows the address it is on and lets you copy it. When your draft changes the page's address, a note says where it is published now and where it will move when you publish.
  • Published shows the page at its live address, even when the draft has moved it. An entry that has never been published says so.
  • Fields (or Cmd J) lists every field of the entry, marks the ones with unsaved changes, and jumps to the one you pick while outlining it on the page. Turn on Follow the page and the form keeps up as you scroll the site.
  • Full-page preview gives the page the whole screen and floats the form over it in a panel you can move and fold away. Unsaved changes show on the preview with a Save draft button.
  • Editor
  • Preview

Preview your site beside the editor

Press Preview on an entry and your own website opens next to the form, showing the draft you are editing. Click a field and its spot on the page lights up.

What changed
  • Switch between Draft and Published to compare what you are writing with what visitors see now. An entry that has never been published says so instead of showing a broken page.
  • Focus a field and the preview outlines where it appears on the page and scrolls to it. Click text on the page and the editor jumps to the field that holds it.
  • Save a draft and the preview updates in place, keeping your scroll position.
  • Check the phone layout with one click, show every editable spot with Show fields, and drag the divider to give the preview more room. While the preview is open, the entry's details move to a slim bar above the form so the text keeps its width.
  • Your site needs a preview address in Settings, a route on the model, and the small overlay from @capacms/sdk for highlighting. Without the overlay the preview still works and says what to add.
  • Admin

A calmer sidebar

The sidebar is easier to scan: simpler icons, folders that do not push their contents halfway across, and folder names that get the room they need.

What changed
  • New icons you can tell apart at a glance: a box for Models, a squiggle for Content, a mountain and sun for Media, stacked blocks for Pages, tiles for the Dashboard and linked dots for Integrations.
  • What sits inside a folder now starts under the folder's name instead of far to the right of it, and each level deeper steps in a little less.
  • Counts sit at the right edge with space between them and the name, and the folder buttons only appear when you point at a folder. Long folder names show far more before they are cut short.
  • Pages appears in the sidebar once your project has pages. Give a model a route and it shows up; until then it stays out of the way.
  • Workspaces

Name your own folders in the sidebar

Your workspace is now a list of folders you name, and a folder can hold anything: models, entries and media side by side.

What changed
  • The fixed Models, Content and Media headings are gone. Make a folder called Pages or Launch and put whatever belongs in it, whatever kind of thing it is.
  • Folders go inside folders, so a big project can have a shape instead of one long list.
  • Your existing workspaces keep everything they had, in folders named after the sections they came from. Rename them to whatever you actually call them.
  • New workspace offers a starting point: Blank, Website (Pages, Components, Settings, Media) or Catalog (Products, Collections, Assets). Every folder it makes can be renamed or removed.
  • Categories moved out of the sidebar to the Category filter on Models and Content, where you were already using them. Manage categories at the bottom of that filter renames, adds and deletes them.
  • API

The API for the screen you are on

A narrow panel that shows the API request returning exactly the entries in front of you, filters and sort included, ready to copy into your code.

What changed
  • Open it from the entries list, a single entry, the field editor, or Content once you have filtered it. It shows the request, the fields it asks for, and the filters it carries.
  • Your search, your sort and your tag chips come across as real query parameters, so the panel is the view you are looking at rather than a blank starting point.
  • Filters the API has no equivalent for are named, with the reason. A draft filter is one example: whether a key sees drafts is a property of the key, not of the request.
  • Pick the fields you want from a checklist, or type them. Either way the panel keeps the request valid and tells you where it is wrong before you send it.
  • Copy the request, a fetch call or an SDK call. Paste a key and run it from the panel to see the real response.
  • Admin
  • Preview

See which pages your content is on

Capa now knows about the pages on your website, so before you unpublish something you can see exactly where it appears.

What changed
  • Pages is a new item in the sidebar. It lists every page of your site Capa has seen, busiest first, with the models behind each one and when it was last read.
  • Open a page to see the entries it shows, the reads it made over the last 30 days, and what each read asked for. If a page is pulling far more than it renders, that is where you will notice.
  • Capa also reads that traffic for you and says what looks expensive: a read that pulls the whole entry, the same model fetched one row at a time, traffic that never reaches the cache, or a site built from an older version of your models. Each suggestion carries the numbers behind it and, where there is a fix, a line you can copy straight into your code.
  • Open any entry and, if it appears on a page, a small marker beside the title says so. Click it for the list, with a link to each page.
  • Give a model a route in Model settings, for example /blog/[slug], and Capa knows where its entries are published. Add your site's address in Settings > Project and Open on page will open any entry, drafts included, on your real site.
  • The reads counted here are the times a page asked Capa for content. A page served from a cache never reaches us, so treat the numbers as a comparison between pages rather than as visitors.
  • Admin

The bell tells you what happened

The bell at the top of Capa now shows what needs you and what finished while you were away, with a count of what you have not read yet.

What changed
  • A publish that failed overnight is at the top of the menu with a Retry beside it, so you can deal with it without going looking for the screen it lives on.
  • Finished work is there too: a bulk publish that completed, a schedule that fired, a field change that converted your entries.
  • Invitations nobody has answered show up for the people who manage the team, and the newest What's new entry sits at the bottom.
  • The count clears once you have had the menu open for a moment, or straight away with Mark all read. Anything that still needs you stays in the list.
  • Admin
  • API

Developer tools have their own place

Settings had quietly become the drawer everything went into. The developer half of it is now its own section in the sidebar, so Settings is the handful of things you actually own.

What changed
  • Developers holds Queries, Keys, Requests, Cache and Webhooks. Integrations sits beside it, and both are one click from anywhere.
  • API keys have one home. Members still points at them, so inviting a teammate and giving a build server a key are next to each other.
  • Settings is Profile, Members, Billing and Publishing. Publishing stayed, along with the dot that appears when a scheduled publish has failed.
  • The cache screen is three views instead of one long page: what the cache is doing, purging something, and the rules. Purging now works out the blast radius on its own as soon as you have chosen what to affect.
  • Every old address still works. A bookmark of the API explorer, the request logs or the keys page lands where that screen lives now.
  • Publishing

Publish a whole model at once

Publish every draft in a model from one place, see exactly what will go out before you confirm it, and get told when a scheduled publish fails.

What changed
  • Publish all drafts, on a model page or a Models row, shows you the count first: how many are ready, how many are written against older fields, how many are missing something. You confirm a number, and that is the number that publishes.
  • Narrow it down by folder, tags, when it was last updated or a word in the title, and the count follows as you change it.
  • Over fifty entries the publish runs in the background and a pill counts it out, so you can carry on working and still get the receipt.
  • Unpublish is now beside Publish when you have entries selected. It takes them off the public API and keeps their drafts.
  • A failed scheduled publish shows on the dashboard and puts a dot on Settings > Publishing until you retry it or cancel it.
  • Published one thing by mistake? The confirmation now has an Undo for eight seconds.
  • API

Create an API key that can only do one job

Developers > Keys now mints keys with a name, an expiry and a precise list of what they may do, so a key on a build server cannot delete your content.

What changed
  • Pick a starting point (Read only, Content writer, Full integration, Schema builder) or tick exactly what the integration needs, and limit entries or models to a shortlist.
  • The secret is shown once, right after you create it. Rotate a key to mint a replacement and give the old one a grace window, so you can deploy without a gap.
  • The list shows what each key may do, where it works, when it was last used and when it expires, and offers to recreate an old key with the same grants.
  • Webhooks

Webhooks for publish events

Capa can tell your site the moment content changes, so a page can rebuild itself instead of waiting for someone to notice.

What changed
  • Point an endpoint at your site, pick the events it should hear about, and every request arrives signed so your server can prove it came from us.
  • Each delivery is kept for 30 days with the exact request we sent and the answer we got back, and you can redeliver a failed one from the list.
  • An endpoint that keeps failing is paused automatically rather than retried forever, and resuming it offers to send the events it missed.
  • Publishing

Schedule a publish, or publish many entries at once

Set an entry to go live at a time you choose, in the time zone you choose, and publish a whole selection in one action.

What changed
  • You pick a wall clock time and a time zone, and Capa publishes at that moment wherever you happen to be when you set it.
  • The entry says what it is doing in plain words: draft, published, draft ahead of what is live, or scheduled for a named date and time, with Change and Cancel on the same line.
  • Settings has a Publishing list of everything scheduled, running, finished or failed, grouped by the action that created it, so an overnight failure is visible the next morning with a Try again.
  • Admin
  • API

Lists sort the way people read

Sorting by title, name or slug orders text the way a dictionary does, not by character code, and it now does so identically on every surface.

What changed
  • Capital and lower case letters sit together, so "apple" no longer lands after "Zebra" in a list sorted A to Z.
  • Accented and punctuated titles fall where you would look for them, in the admin lists and through the API alike.
  • Team

Invitations that land where they should

Accepting an invitation now takes you into the project you were invited to, even when you already had another one open.

What changed
  • Someone who already has a Capa account is switched into the new project and told they were added, instead of being dropped back where they started.
  • If the wrong account is signed in, the invitation page says so and offers to sign out and use the right one.
  • The invitation email says "added you to" and asks existing users to sign in with the account they already have.
  • Models
  • Editor

Design your own entry editor with the layout builder

A model's editor no longer has to be one long column of fields. You arrange the screen your team actually uses.

What changed
  • Drag fields into rows and groups so the things that belong together sit together, and the editor looks the same for everybody on the project.
  • A related entry can be edited in place instead of sending you to another screen and back.
  • Leaving the builder with unsaved changes asks first rather than quietly discarding the layout.
  • Editor

One entry card, with the field editor a click away

Entries look the same wherever they appear, and getting from an entry to the fields behind it no longer means hunting for the way in.

What changed
  • One card design everywhere entries are shown as cards, so the same entry does not look like two different things on two screens.
  • The collapsed half-view is gone, and the field editor is one visible click from the entry you are reading.
  • Admin

Right-click anywhere, recent projects, clearer drag and drop

A set of small things that add up: the project switcher remembers where you have been, and every row answers a right-click.

What changed
  • Projects are listed by the ones you opened most recently, so the switcher stops being an alphabetical hunt.
  • Right-click a row, a folder or an item in the left nav and get the same actions its menu offers.
  • Dragging shows what you are carrying and where it will land, and a folder opens on a single click.
  • Content lists can show Category and Tags as columns.
  • Media
  • API

Images resize and convert on the fly

Ask an image URL for the size and format you want and Capa makes it, so your pages ship smaller pictures without anyone exporting anything.

What changed
  • Add width, height, quality or a format to a media URL and the file comes back that way, cached at the edge for a year.
  • Name the format you want, such as webp or avif, and the file is converted for you. Automatic per-browser selection is built and waits on one CDN setting before it works through the edge.
  • Camera metadata is stripped by default, photos are rotated the right way up first, and files we cannot transform are served untouched rather than failing.
  • Workspaces

Saved workspaces, shared or private

Keep more than one arrangement of the left nav and switch between them, instead of one menu that has to suit everybody.

What changed
  • A workspace can be shared with the team or kept private to you, and a project can name the one new members start in.
  • Each workspace chooses which sections it shows, so a writer's menu does not have to carry the developer's models.
  • Workspaces

Your left nav is now your folder structure

The left side of Capa shows the models, content and media you actually work on, arranged in folders you make yourself.

What changed
  • Drag a model, an entry or a media folder into the nav and it stays there, for you or for the whole team.
  • Folders hold items rather than more folders, so the menu stays one level deep and readable on a small screen.
  • Clicking a folder opens its list filtered to that folder, and the same tree is available on a phone under Account.
  • Admin

A calmer, faster admin

Capa has been rebuilt around the content instead of around its own chrome. Less framing, bigger titles, and a real phone experience.

What changed
  • Outlined boxes are gone. Pages separate by tone and a faint hairline, so the entry you are reading is the loudest thing on screen.
  • Lists share one table with sorting, filter chips and column choices, and every list page opens the same way.
  • On a phone Capa is a native-feeling app with a bottom tab bar, full-width lists and bottom sheets, not a desktop page squeezed small.
  • Light and dark are both first class, and the whole app follows the one you set here or the one your system asks for.