[NOW AVAILABLE] 👋 Hey Content Agent, tell me what you do that other AI tools can’t

Stop publishing page by page

Content Releases

Group changes. Preview together. Publish at the right moment. One click.

A software interface for "Feature release: Analytics" showing a list of actions, document types, and last edited times, with a "Run release" button.

Content Releases 101

See how to launch a site-wide campaign

0. The highlights

Ship complex launches with confidence

  • A release management screen for 'Upcoming: Spring Release' on March 1, 2025, showing content actions.

    Launch everything at once

  • Mobile screen displaying "Spring Release" text highlighted for editing over a dandelion background, with design UI elements.

    Preview before publishing

  • A calendar widget displaying March 2026, with the 1st of the month highlighted in blue and a time selection showing 10:00.

    Schedule or ship when ready

  • A table of active releases showing columns for Name, Time, and Edited. The Spring release row is highlighted, dated March 1, 2026, and edited 1 day ago.

    Stack releases without conflicts

Launch everything at once

Bundle related changes into a single release so everything goes live together at the right time and without issues.

Preview before publishing

See exactly how all your changes look together before going live so you can catch issues in a safe environment.

Schedule or ship when ready

Set specific dates and times for automated publishing or mark releases as ready to ship whenever the moment is right.

Stack releases without conflicts

Prepare holiday content while summer campaigns are still pending as the system automatically handles overlapping changes.

1. Create a new release

Separate campaigns from daily edits

A content management interface displaying the "Urban Explorers monthly edition" release, listing various travel guides and content items with actions like Add, Change, and Unpublish.

Bundle changes across documents

Launch homepage, product pages, and navigation together without manual tracking or forgotten pieces.

Unpublish documents on schedule

Remove content as part of a release for time-sensitive campaigns or expired promotions.

Work without cluttering drafts

Prepare launch content in isolated releases while regular updates continue in drafts.

Request a demo

2. Preview and validate

No more launch day surprises

A webpage displaying a music festival lineup with "Static" highlighted, alongside an open editor panel showing its details for editing.

Validate before publishing

Releases make it easy for you to fix validation errors and prevent you from publishing broken content.

Preview the future state

Preview release impact across your entire site with visual editing, not just individual pages.

Toggle releases to preview layering

Turn releases on and off to preview how your site looks as campaigns layer together, showing which changes take priority.

3. Schedule release

Nail your launch timing

A "New release" dialog with a date input field showing "2026-01-28" and an open calendar widget highlighting January 28, 2026.

Schedule to the minute

Set precise publish times for coordinated launches, even at 3 AM or during peak traffic.

Publish when ready

Mark releases as ASAP and publish when you're ready instead of setting a scheduled time.

A mouse cursor points to a "Run release" button with an upward arrow, on a dark, motion-blurred background.

Control releases through code

Use the API to create, manage, and publish releases from your CI/CD pipeline or trigger based on external events.

const {releaseId} = await client.releases.create({
  metadata: {
    title: 'New bike release',
    releaseType: 'asap'
  }
})
Request a demo

4. Stack releases

Multiple releases, zero conflicts

A dashboard displaying active releases with their names, scheduled times, and last edited times.

Track every change

Complete audit trail shows who modified what and when.

Work on multiple releases

Queue up Black Friday and Cyber Monday campaigns ahead of time so both go live at the right moment without manual intervention.

Revert when needed

Roll back published releases to restore a previous state.

Copy between releases

Copy document versions across releases without starting from scratch.

Query any release state

Use Content Lake Perspectives to programmatically access content as it exists in drafts, published, or any release layer.

import {createClient} from '@sanity/client'

const client = createClient({
  ...config,
  perspective: 'release-id1',
})