Exactly what's supported. With a date on it.

Real form editing, verified: all eight content-control kinds round-trip, protected forms honour their allowed ranges, and a wrong password fails closed into read-only.

Open a live example →A federal quality-assurance form with 18 fillable content controls. Opens fast.

The macro you inherited still runs — here, on your file, without Windows and without Office. The engine reads the real VBA project out of the document, runs the entry point you name over the document's actual text, and shows you what changed before anything is written: the run happens on a copy, and the copy only replaces your file when you say so. Nothing runs unattended — every entry point needs your explicit permission, and without it the answer is a refusal, not a silent skip. 215 checks stand behind that behaviour.

Open the document with the macro →A commercial offer that still has its macro: Offer.PrepareForClient fills in the client, the number and the dates, and turns the status line from DRAFT into READY TO SEND. Open it, ask the assistant what the macro does — it reads the VBA itself — and then ask it to run the macro and show you every paragraph it would change, before and after. The run writes nothing: each change comes back as a card with an Apply button, and the document stays exactly as it was until you press it.

Right-to-left direction lives in the document model and survives open and save untouched.

Open a live example →An Arabic right-to-left document — the Library of Congress romanization tables, with the direction visible on every line.

Embedded objects survive open and save lossless, the engine tells you they are there — and never executes them.

Open a live example →This report's charts are linked to an external workbook — the editor opens it in protected view, with an honest enable button, and never runs the link. Large file: give it a moment.

Tables — merged cells included — come back exactly as they went in.

Open a live example →A 32-page annual report full of real tables. Large file (33 MB): give it a moment.

Your pictures and everything drawn around them stay in the file, unchanged.

Open a live example →Dozens of photographs across a real field report. Large file: give it a moment.

Your bulleted, numbered and multilevel lists come back exactly as written, and the preview draws the ones it has been proven on. Where it has not been proven, it says so instead of guessing.

Open a live example →A two-page brochure with real bulleted lists. Opens fast.

Comments, replies and their anchors round-trip untouched — and editing a comment goes through the same proven path as forms (see Forms).

Open a live example →A 24-page working draft with real reviewer comments and tracked changes still in it.

Headers and footers survive open and save untouched.

Open a live example →Page footers run through the whole report. Large file: give it a moment.

Footnotes and endnotes survive open and save untouched.

Open a live example →A short research summary with six real footnotes at the bottom of the page. Opens fast.

Hyperlinks and bookmarks keep working after the round trip.

Open a live example →Real links and bookmarks inside a real report.

Style definitions, style inheritance, themes and the font table come back exactly as they went in.

Open a live example →A fully styled report — headings, theme colours, real fonts.

Section properties and page setup — landscape orientation included — are preserved.

Open a live example →A one-page flyer whose layout hangs on a real section break. Opens fast.

Document properties and settings survive open and save untouched.

Embedded HTML content is kept as an opaque payload rather than converted lossily.

What this page claims about drawing your document is deliberately narrow: only what has been measured against the real file. Anything unproven is refused out loud rather than drawn approximately. The live demo often draws well ahead of this list — this list never runs ahead of the engine.

Open the live demo →The real editor, in your browser, on a real published file.

The worksheet-function surface is the largest block on the map — so rather than claim it, we counted it: one workbook, one real formula per function, and what did not compute named beside what did.

Open a live example →384 worksheet functions verified value-by-value in this cabin (362 exact, 22 to more decimal places) of the 451 the engine's own map calls live, across 9 categories — and the book names, row by row, the 54 that return no value yet, the 8 that differ and the 5 volatile ones checked by property instead of value.

Multiple sheets, the sheet tab strip, and formulas that reach across sheets — sheet lifecycle, freeze panes, fill, find and page setup all sit in this block.

Open a live example →Three sheets you can switch between, with the Summary sheet pulling its numbers out of the other two.

Currencies, percentages, dates, times, fractions, scientific notation and text formats are read from the file and shown as the file asks — measured on the same browser cabin the live example runs in.

Open a live example →Currency and percentage cells throughout — the totals are formatted by the workbook, not by us.

Sort and filter, tables and their contextual commands, validation and the data-tool block — with the one command that is genuinely not ready named out loud.

Open a live example →A workbook with two real table objects: the header carries filter buttons, and the assistant can name every part of the book beside them.

The registry counts this area as finished. A separate hand check against Microsoft Excel does not. We are not going to pick the flattering one: the hand check found fourteen chart properties missing — gradient, picture, texture and pattern fills; reflection, glow, soft edges, bevel and 3-D; point editing; live preview — and the effects pane is not written back to the file. Treat the smaller claim as the true one.

Open a live example →A Bureau of Labor Statistics chart sheet — a whole sheet that is nothing but one chart. Two series, 157 values, every U.S. state along the axis, drawn from the workbook's own data sheet next to it.

PivotTable layout, styling, printing and the analysis commands — with the OLAP side kept deliberately out of scope. The live example is the one real PivotTable workbook in our public corpus: the U.S. Bureau of Labor Statistics labor-composition dashboard — a PivotTable with its cache, a slicer, a 25,000-row table and a chart across three sheets. It used to take 164 seconds to open (a quadratic scan and a whole-workbook recalculation the first screen never needed); it now opens in about eight.

Open a live example →A 1.2 MB dashboard from bls.gov, untouched. The “Chart” sheet draws the PivotTable, its pivot chart (four series, 2005–2019) and the three slicers with their items and current selection — the slicers are a faithful snapshot, not a live filter yet. The “Data” sheet is the 25,620-row source table and takes a few seconds to arrive.

Get & Transform, connections and the query surface around them: the queries Excel authored are read with their steps, and new ones are written in the Power Query Editor — eleven data sources, Enter Data, Applied Steps, the formula bar, Close & Load back to a sheet.

Open a live example →The same workbook, yours to try: an order export with the query SalesByRegion — open Data → Queries & Connections, or Get Data → Blank table and build one.

Scripts and the automation surface are on the map. A macro is never run natively: the engine runs a named macro on a COPY of the workbook, shows every cell it would change, and writes nothing until a person presses Apply. External objects a macro asks for go through the engine's broker — allowed per class, per session, by the person, and every call is journaled.

Open a live example →An order desk workbook: press ✦ Agent, allow the two object classes the macro asks for, run SummarizeOrders on a copy — one changed cell previewed, 28 brokered calls in the journal.

Sheet and range protection: locking a sheet, refusing an edit to a locked cell, taking one to an unlocked cell, and keeping all of that through the save.

Open a live example →A U.S. Department of the Interior workbook whose sheet is password-protected in the file itself. Type into any cell: the editor refuses with the same message Excel gives, and the cell keeps its value. We do not have the password either.

Opening and saving the workbook formats, the trust decisions around them, and recovery after a bad exit. There is nothing to press here on purpose: this area is about what happens to your file, not about something a demo page can show you.

Comments and notes, spelling, the accessibility checker and the review block around them.

Open a live example →A Census Bureau conference planner with reviewer notes from four people still in it. It opens on the sheet that carries them: the notes are drawn where they were anchored, each with its author.