I'd like to request native autosave functionality in the Strapi v5 Content Manager, covering both periodic autosave (every X seconds) and save-on-blur (when leaving a field). This is a common UX expectation in modern CMS platforms and its absence is a frequent source of data loss for editors.

Problem

When working in the Content Manager, there is currently no mechanism that automatically saves a user's progress. If a user accidentally closes the tab, navigates away, or experiences a browser crash, all unsaved work is permanently lost. This is especially painful when editing long-form content or complex entries with many fields.

This issue affects:

Content editors working on large or long-form entries

Teams using Strapi on the Community plan, who have no access to plugin workarounds in some cases

Any user on an unstable connection or device

Proposed Solution

Add a native autosave mechanism to the Content Manager with the following behavior:

Periodic Autosave — Automatically save the current entry as a draft every configurable interval (e.g., every 30 seconds), only when changes are detected.

Save on Blur — Trigger a save when the user moves focus away from a field.

Visual Indicator — Show a subtle status indicator (e.g., "Saving…" / "Saved") in the toolbar so editors know their work is being persisted.

Draft-safe — Autosave should save to draft state only, without triggering a publish, to avoid unintended content going live.

Proof of Concept (Community Workaround)

To validate this is technically feasible within the current architecture, I implemented a custom autosave solution on Strapi v5 using the admin panel extension injection system:

Injected a custom React component into the Content Manager via admin/src/app.tsx

Used a MutationObserver to detect DOM-level changes in the editor

Triggered the Strapi PUT API (/api/{contentType}/{id}) on a debounced interval when changes were detected

Displayed a live autosave status badge in the toolbar

This worked reliably for both simple and relational fields. The fact that this could be achieved externally confirms that native support at the core level is both feasible and would be significantly more robust.

Why This Should Be Native

A community workaround via MutationObserver is fragile — it depends on DOM structure that can change between versions

It requires each team to re-implement the same logic independently

Native autosave would have access to the internal form state directly, making it more reliable, accurate, and maintainable

It aligns with UX standards set by other CMS platforms (WordPress, Contentful, Sanity, etc.)

Environment

Strapi Versionv5 (latest)DeploymentSelf-hosted / CloudPlanCommunity (no plugin access)

Additional Context

This feature has been discussed informally in the community for some time. Autosave is considered a baseline expectation for content editing tools in 2025. I believe adding it natively — even behind a feature flag or admin toggle — would significantly improve the editor experience for all Strapi users.

I'm happy to contribute or provide more details about the PoC implementation if helpful.