What you can do

Each example starts from a problem people actually run into, then shows what changes and how to begin.

See document changes in code review

Reviewers see the changed pages instead of "binary file changed".

Who it's for: Teams that keep specifications, design documents or quotes in a Git repository.
The problem today: When a PowerPoint, Excel file or PDF changes, the pull request only says "binary file changed". To see what actually changed, someone has to download the file and open it.
With document-svg: Every changed document is converted into SVG pages that can be downloaded from the workflow run. A comment lists how many pages and warnings each document has, so you can tell at a glance which files need a closer look.
How to begin: Add one short workflow file that calls the included workflow. Nothing needs to be installed on your side.

Show users their documents without Office on the server or a paid viewer.

Who it's for: Developers of internal systems and web services that need to show files their users upload.
The problem today: Previewing Office files usually means installing Office or a converter on the server, paying for a viewer SDK, or sending the files to an outside conversion service.
With document-svg: Call it from Node.js or Python and you get one SVG per page, ready to show as an image. Conversion finishes inside your server, so the file never leaves it.
How to begin: Install the npm or pip package and call the convert function. For PDF, Word, Excel and PowerPoint only, there is also a WebAssembly version that converts inside the browser (you build it yourself).

Diagrams are rebuilt from text every time the documentation is.

Who it's for: Engineers who put architecture diagrams in design documents or a wiki.
The problem today: When a diagram is drawn in a separate tool and pasted in as a picture, the code moves on and the diagram stays old. Nobody can tell who changed it or when.
With document-svg: Keep diagrams as draw.io, Mermaid, PlantUML, D2 or Graphviz text next to the code, and turn them into SVG every time the documentation is built. Diagram changes get reviewed like code changes.
How to begin: Add one conversion command to your documentation build.

Look at plans, boards and 3D models from a web page.

Who it's for: People in manufacturing and construction who check drawings but don't make them, and the developers who build tools for them.
The problem today: Checking a single drawing often needs expensive CAD software and a licence. Giving one to everyone who reviews drawings isn't realistic.
With document-svg: Floor plans (DXF), circuit boards (Gerber), machining paths (G-code) and 3D models (STL, OBJ, STEP) can be shown on a web page or dashboard.
How to begin: Look up your file type in the format list to see how much of it gets drawn. Some formats show a summary of their contents rather than the full drawing.

Tables, charts and formulas that look the same every time.

Who it's for: Anyone producing regular reports or technical documents automatically.
The problem today: Everyone turns tables and charts into pictures their own way, and the result looks a little different every time.
With document-svg: CSV tables, chart data and LaTeX formulas become SVG images that come out identical on every run. They stay sharp when zoomed, so they print well too.
How to begin: Prepare the data file and convert it with the same command as any other document.

One dependable step instead of screenshots and browser automation.

Who it's for: People who want an AI agent to review or produce documents.
The problem today: Showing a document to an AI usually means screenshots or automating a browser. Both break easily, and nobody can tell how much the AI actually saw.
With document-svg: Give the assistant a fixed routine: convert the file into pages, then check the report for anything missing. If part of the file didn't convert, the assistant can see that in the report.
How to begin: Install the plugin for Claude Code or Codex, or let the assistant run the command directly.

Package SVG pages as PowerPoint, Word, Excel, draw.io or CAD files.

Who it's for: Developers of tools that create or edit SVG and need to hand the result over as an Office or CAD file.
The problem today: Colleagues can't open a folder of SVG files in the software they use every day.
With document-svg: SVG pages can be packaged as PowerPoint, Word, Excel, PDF, draw.io or DXF files. What comes back is how it looks; paragraphs, cells and formulas are not rebuilt. A draw.io diagram comes back editable if its source was embedded in the SVG.
How to begin: Point the write-back command at a folder of SVG pages.