# Roadmap

> The Fabric.js editor roadmap for this package: what is stable in 1.x, what may come next, and how to send feature requests through GitHub issues.

Source: https://fabricjs-document-engine.jscrate.dev/docs/overview/roadmap
Last updated: 2026-09-28

This Fabric.js editor roadmap lists what is settled and what is being considered. Nothing below is promised by a date. Plans change when users report what they actually need.

## Stable in 1.x

The document format, the public API and the adapter contracts are frozen for every 1.x release. New releases add features without breaking what you built. The [compatibility](https://fabricjs-document-engine.jscrate.dev/docs/production/compatibility) page lists the tested browsers and Fabric.js versions.

## Being considered

- **More storage examples**, such as Supabase, Firebase and IndexedDB as the main store.
- **Multi-page documents**, where one document holds several canvases.
- **Smaller history steps for text**, so long text edits use less memory.
- **Fabric.js 8**, once it is released, tested the same way as 6 and 7.

## Not planned

- **Real-time collaboration.** Revision checks catch conflicts, but live co-editing needs a different design, such as CRDTs.
- **A built-in toolbar.** Your editor's UI stays yours.

## Feature requests

Open a request in [GitHub issues](https://github.com/re-sohail/fabricjs-document-engine/issues). Describe the problem in your editor, not only the solution you have in mind. Feature requests with a real use case shape the Fabric.js editor roadmap more than votes do.