Free4AllHubIsolated workflow proof

Create something useful

A document you can come back to

Write a clear note, guide or small plan. Use real headings, lists and links, then keep an editable project and export a Word copy.

Local to this tab. No automatic saving. Nothing you type or open is uploaded. Refreshing or closing loses your work. Download editable JSON and reopen it to check your copy. Files are plain, unencrypted and may contain private information.

1. Start or reopen

JSON restores this workbench’s version 1 project. DOCX imports supported text and structure, not page layout. Tables, images, nested lists, comments, tracked changes, fields and other unsupported content are rejected, not silently removed. Keep your original. HTML is not an import format.

Practice first: download a fictional garden plan DOCX, then open that file above. Change the meeting time from 10 am to 11 am, save JSON and export Word. Reopen both saved copies and check the revised time. This sample contains no real personal information.

2. Write with structure

Use Heading 1 for the document’s main heading, then Heading 2 and 3 in order. Use specific link text. Tab moves to controls and out of the editor; Ctrl/Cmd+B and I format selected text. Enter continues a list; Enter again on an empty item leaves it.

3. Keep and use your document

Reopen JSON here to keep all editor structure. Simple DOCX text can also reopen, with review; DOCX containing nested lists or other unsupported structures cannot. DOCX keeps the supported headings, lists, links, bold and italic for other document editors. HTML is a semantic readable copy. Neither export is a pixel-perfect Word preview or a guarantee of accessibility. Check the exported file in the app you will use. Word export runs in a local worker with a 30-second limit. Editing or opening another document cancels an in-progress Word export.

  1. Download the editable project and keep the previous version.
  2. Open a fresh tab, choose that JSON and review it before replacing.
  3. Revise a sentence, download again, and reopen the revised copy.

Optional: put the editable JSON in Keep & reopen alongside a manually exported Learn brief. Later, download the unchanged document from the bundle and review it here before opening. Keep DOCX and HTML separately. These plain files are not encrypted or automatically redacted; a bundle does not convert, synchronize or publish your work.

Ready. Start blank or try the fictional example.

What this focused tool does and does not do

Supported: paragraphs, heading levels 1–3, up to four nested list levels, HTTP/HTTPS links, bold, italic and line breaks. Maximum 100,000 text characters and 2,500 document nodes. Limits reduce accidental overload but cannot guarantee device performance.

No images, tables, pagination, templates, comments, tracked changes, collaboration, full-fidelity Word import, automatic backups or cloud storage. Links do not open in the editor. Exported links open only when the reader chooses them. A download request does not prove that a file was saved.

Editing uses ProseMirror. DOCX export uses docx. Bounded DOCX import uses fflate and sax in a cancellable local worker with a 10-second limit. Dependencies are bundled locally with their notices; there is no runtime CDN. This proof has not been screen-reader or real-phone tested.

Dependency licences · Source and workflow notes