What's new

Right-to-left support in the editor

Revise now handles right-to-left languages properly. Text flows from the right, mixed passages (like an English name in an Arabic sentence) render in correct bidirectional order, lists mirror with bullets and numbering on the right, and the cursor moves the way you'd expect. There's a new direction toggle on the Edit tab if you need to set direction explicitly.

Direction survives the round trip through .docx and HTML, and PDF export ships proper Arabic text shaping with bundled Arabic and Hebrew fonts.

Backups

You can now download your whole account as a .zip. Open Settings Backup, pick a format — Word (.docx), plain text, RTF, Markdown, or HTML — and optionally narrow it to a single folder. The archive mirrors your folder structure, and everything converts right in your browser.

The engine behind Revise is now available as the Revise SDK, and today it reached 1.0. It ships in two surfaces: a React component that opens .docx files inside your app — page-perfect rendering, tracked changes, and multiplayer editing over a Yjs provider you own — and a Node entry point that lets your server read, edit, and export the same documents headlessly, no browser required.

One tool contract, browser and server

The 1.0 milestone is convergence: both surfaces now speak the same canonical tool contract — the same document tools the Revise agent itself uses, with typed inputs and structured results. Wire them to any AI agent and your result-handling code is shared verbatim between web and Node. Malformed model input can't crash your agent loop: expected failures come back as structured results, never exceptions.

Tracked changes are the default posture

Server sessions now propose tracked suggestions by default instead of silently rewriting the document — the same safe stance as the editor. Every mutation reports the suggestion IDs it created, and a new review API lists pending suggestions with authorship metadata and resolves them by ID, so your agent can accept its own work and leave a collaborator's pending edits alone.

The full documentation lives at sdk.revise.io, including a complete backend reference. Building something on it? We'd love to hear from you at sdk@revise.io.

Moves are now a first-class tracked change

Until now, moving a passage while suggesting looked like what it technically was: a deletion in one place and an unrelated insertion in another. As of today, cutting text and pasting it elsewhere in the document creates a real linked move — the source shows "Moved from" and the destination shows "Moved here", and focusing either half highlights its partner, even across paragraphs.

Moves resolve atomically: accepting either half keeps the text at its new location, rejecting either half puts it back where it came from, and undo reverts both halves together — you can never strand an orphaned end of a move.

This is Word's behavior, and it round-trips as such. Moves made in Revise export as native Word move markup, and documents with tracked moves made in Word import as linked move suggestions — not a confusing pile of deletions and insertions.

More DOCX fixes

This release also ships a round of .docx fixes: text in shapes and drawings now imports as editable paragraphs instead of disappearing, comment anchors keep their exact range through repeated round trips, exported files are smaller, and large imports are faster.