Most headless CMS platforms can schedule publishing, but they differ in what they schedule (one entry or a bundle), how they handle time zones and references, and which plan unlocks it. Contentful, Contentstack, Storyblok and DatoCMS schedule publish and unpublish for single entries, and the first three also bundle changes into releases; Sanity, Hygraph and Strapi gate scheduling behind paid plans; Payload does it with a background job you must run yourself.
This page compares nine platforms on the features that matter when a campaign has to go live at 00:01 in three time zones. We read each vendor’s documentation in October 2026 and mark where the docs were unclear. Looking for something broader? Start from the headless CMS platform index or our headless CMS pillar.
What does content scheduling mean in a headless CMS?
Scheduling has four separate parts, and platforms cover them unevenly.
- Timed publish and unpublish. An entry goes live, or comes down, at a chosen time. This is the baseline.
- Bundles. Several entries, often in several locales, go live together. Vendors call these releases.
- Time zones. The editor picks a zone, and the schedule stays correct when editors and servers sit elsewhere.
- Delivery. A scheduled publish changes the CMS state. Your site still has to notice. A server-rendered frontend shows the change on the next request; a static site needs a build trigger.
Teams usually underestimate the fourth part. Scheduling in the CMS is a few clicks. Making the site match is an engineering task: a webhook, a cache purge, sometimes an incremental rebuild.
How we evaluated
We checked each platform’s official documentation in October 2026 for five things: whether single entries can be scheduled for publish and unpublish, whether bundles are supported, how time zones are handled, what happens to referenced content, and which plan is required. Where a page did not state the plan, the table says so. We do not quote prices, because they change often; confirm them on the vendor’s pricing page.
Headless CMS scheduling compared
| Platform | How it supports scheduling | Hosting | Free tier | Best for |
|---|---|---|---|---|
| Contentful | Scheduled actions for entries, assets and releases | SaaS | Yes | Enterprise teams with many editors |
| Sanity | Scheduled drafts for one document, Content Releases for bundles | SaaS | Yes, scheduled drafts need Growth | Custom editorial workflows |
| Storyblok | Single story scheduling and a Releases app | SaaS | Yes, plan for releases to confirm | Marketing teams that want a visual editor |
| Hygraph | Scheduled entries and releases | SaaS | Yes, scheduling is Enterprise only | GraphQL-first teams |
| Contentstack | Schedule entries and assets, Releases for bundles | SaaS | Yes | Large multi-brand organisations |
| Prismic | Releases of pages with a date and time | SaaS | Yes, one user | Marketing sites built from slices |
| Strapi | Releases with date, time and time zone | Self-hosted or Strapi Cloud | Yes self-hosted, releases need Growth | Teams that want to own the stack |
| Payload | Scheduled publish and unpublish through a job | Self-hosted, inside Next.js | Yes, MIT licence | Next.js teams that want code-level control |
| DatoCMS | Per-record schedule, per-locale schedule | SaaS | Yes | Multilingual sites with a small team |
The platforms, one by one
Contentful
Contentful’s scheduled actions publish or unpublish entries, assets and releases at a set time, with an optional IANA time zone. A release holds up to 200 entities, counting referenced ones, and you can stack several schedules on one release. The documentation caps pending actions per environment, so a very large calendar needs planning. If a scheduled entry fails validation when its time comes, the creator gets an email. Read more on our Contentful page.
Best for: large editorial calendars. Skip if: you want scheduling that survives cloning an environment, because schedules are not copied into new environments.
Sanity
Sanity replaced its old Scheduled Publishing tool, deprecated as of October 2025, with two things. Scheduled drafts publish a single document at a future time and show up as a one-document release. Content Releases handle bundles. The scheduled drafts page says the feature is available on the Growth plan. A scheduled document is locked until it runs, and Studio blocks a schedule if the draft strongly references an unpublished document. See our Sanity page.
Best for: teams that shape the editing experience themselves. Skip if: you need scheduling on the free plan.
Storyblok
Storyblok offers two routes. Editors can schedule one story from the More options menu next to Publish, choosing date, time and zone. The Releases app groups stories and publishes them together on a schedule, and the frontend reads a release by passing its ID in the from_release parameter. A Management API endpoint, story_schedulings, lets you create schedules from code. Vendor pages disagree on which plan includes Releases, so check the pricing page. More on Storyblok.
Best for: marketers who want to schedule from the visual editor. Skip if: your frontend cannot pass a release ID when previewing.
Hygraph
Hygraph schedules publish and unpublish for an entry or for a release that bundles several entries, per locale. The documentation says scheduled publishing is available only on Enterprise plans. Default limits are 50 pending releases, 50 items per release and 200 pending scheduled items per environment. Unpublishing moves the entry back to the Draft stage. See Hygraph.
Best for: enterprise GraphQL projects. Skip if: you are on a self-serve plan and need scheduling now.
Contentstack
Contentstack lets editors publish or unpublish entries and assets now or later, up to 12 months ahead, and reschedule without cancelling. Releases group entries and assets and deploy to chosen environments now or at a set time. The docs warn that referenced entries are not published automatically unless already live, and suggest scheduling the references first and the parent a few minutes later. Entries must also be in a publishable workflow stage when a release fires. See Contentstack.
Best for: multi-brand, multi-environment organisations. Skip if: you want a lightweight tool without workflow stages.
Prismic
Prismic Releases bundle new pages, edits and deletions, up to 200 pages per release, and publish them immediately or at a chosen date and time. You can preview a whole release on your site. Only Publisher, Administrator or Repository Owner roles can publish, and unpublishing pages inside a release is not supported. The release docs did not state which plan includes the feature. More on Prismic.
Best for: marketing sites with a launch calendar. Skip if: scheduled takedowns are a core need.
Strapi
Strapi Releases group entries into a batch to publish or unpublish together, and a release can be scheduled with a date, time and time zone. The content type needs Draft and Publish enabled. Releases are available on the Growth and Enterprise plans, so the free Community Edition does not include them. See Strapi.
Best for: teams that want a self-hosted CMS and will pay for releases. Skip if: you want scheduling in the free edition.
Payload
Payload supports scheduled publish and unpublish on collections and globals by setting versions.drafts.schedulePublish: true. Each schedule creates a background job, so the app must run the jobs queue; otherwise nothing fires. Access control applies to those jobs too, so a user who cannot publish cannot schedule a publish. It schedules single documents, so bundles need your own convention. See Payload.
Best for: Next.js teams that want control and a free licence. Skip if: you cannot run a job runner in production.
DatoCMS
DatoCMS schedules publish and unpublish from a calendar icon next to the Publish button, and schedules can be set per locale. Linked records must be published at that time as well, either beforehand or by the system when the schedule runs. A build trigger setting can start a rebuild after a scheduled publication finishes. The API exposes scheduled publication and unpublishing as separate resources. See DatoCMS.
Best for: small teams running several languages. Skip if: you need bundled releases.
How to choose
- Campaign launches across markets: pick a platform with releases and time zones: Contentful, Contentstack, Storyblok or Strapi on a paid tier.
- Single articles on a timer: any platform here works. Payload and DatoCMS are the cheapest to run.
- Strict approvals: Contentstack’s workflow stages and Contentful’s roles fit regulated teams.
- Static frontend: confirm the webhook fires on a scheduled publish and that your host can rebuild in time.
- Directus: its versioning docs describe manual publishing only. People build schedules with Flows; treat that as custom work.
Scheduling is rarely the deciding factor alone. Pair it with the rest of your requirements; our free headless CMS comparison and open-source headless CMS comparison cover the budget side. If you want a second opinion on a shortlist, our headless CMS agency team runs short audits.
