2 posts tagged with "source-editor"

Most Confluence users never see it, but every page is stored as an XML document in Confluence's storage format — a specific XHTML dialect with custom tags for macros, layouts, and embeddings. The visual editor hides this. But sometimes the only way to fix a problem is to edit that XML directly: a macro is corrupted and won't render, a copy-paste introduced broken formatting, or you need to find-and-replace a URL across a long page that the visual editor can't reach.

Confluence exposes the storage format through its REST API, but there's no built-in visual editor for it. Raw Storage Source Editor for Confluence adds one — a Monaco-powered editor that opens the raw storage XML of any page, with format, find-and-replace, and (in the Pro edition) a diff view. This guide covers when and how to use it safely.

Confluence stores every page as XML in a format called "Confluence storage format." Most users never see it. But if you have ever tried to fix a broken macro, remove hidden formatting artifacts, or bulk-edit repetitive markup, you know the rich text editor alone is not enough. You need direct access to the underlying source.

At NGPILOT, we built two apps for exactly this purpose: Raw Storage Source Editor for Confluence (free) and Raw Storage Source Editor Pro for Confluence (paid). Both let you open, view, and edit the raw XML behind any Confluence page. This post compares them feature by feature so you can pick the right one for your team.