Rich Text Editor: Format Documents in the Browser Without Installing Anything
You open a page, click into the document, and start typing. Selecting a word and pressing a toolbar button makes it bold. That is the whole contract of a rich text editor: the text on screen already looks the way it will look when you hand it to someone else.
This editor takes that contract seriously and keeps the machinery in the browser. There is no account, no upload step, no document sitting on a server waiting for a subscription. What you type stays on the machine you typed it on, and the export buttons produce a file at the moment you click them.
The sections below walk through every part of the interface: the marks, the block types, alignment and sizing, tables and code blocks, the character limit, the counters, and the six ways to get the document out. Numbers and labels match what the tool actually shows, so you can follow along with the page open next to this text.
What does a rich text editor do that plain text cannot?
Plain text gives you characters and line breaks. A rich text editor gives you structure. A line can be a paragraph, a first-level heading, a quote, or a list item, and the difference is stored as structure rather than as decoration.
That distinction matters because structure survives export. When a paragraph becomes a Heading 2, the page carries a real level-two heading underneath, so a search engine reads a section title, a screen reader can jump between sections, and a Markdown file keeps ## in front of the line. Bold text applied to running prose carries a strong or emphasis element, not a picture of bold text.
The tool follows the modern pattern: a contenteditable surface, a toolbar that reports the current state of the cursor, and a plugin layer that keeps the document model in sync with what you see. The visible result is simple. Put the cursor in a line, the block dropdown reads Paragraph. Put it inside a heading, the dropdown reads Heading 2. Select a word that is already bold, the Bold button lights up. Nothing has to be remembered.
Where this becomes practical is the handoff. Rough notes turned into a structured document, a support reply with a numbered list, a README section with code and a table, all of them start as plain typing and end as markup somebody else can consume. The editor covers that path in one screen.
How do the marks and the block types differ?
The toolbar splits formatting into two families, and keeping them apart explains most of the behaviour you will see.
Marks apply to a selection of characters: Bold, Italic, Underline, Strikethrough, Inline code, Superscript, Subscript. They can be combined, and they nest inside whatever block holds the text. Select half a sentence and make it bold, the rest of the paragraph stays regular.
Blocks change what a whole line is. The block dropdown offers Paragraph, Heading 1 through Heading 6, Quote, Bulleted List, Numbered List, Checklist and Code Block. Choosing one converts the current line and, when a range is selected, every line inside it.
The split has consequences worth knowing.
- Headings carry hierarchy. Use one Heading 1 for the document title and let section titles sit at Heading 2, subsections at Heading 3. The table of contents panel is built from that hierarchy, so a page with everything at Heading 1 produces a flat, useless list.
- Lists nest. Increase indent turns a list item into a sub-item, decrease indent pulls it back. Numbered lists renumber themselves after insertion and deletion, which is the main reason to use a real list instead of typing digits.
- Checklists are a block type, not a character trick. Each item gets its own checkbox state, and the state travels with the document.
- Quote is for quoted material, not for indented text. Indentation is a separate control and does not change the meaning of a line.
- Code Block keeps whitespace and monospace formatting, so indented code stays indented. Inline code is for a function name inside a sentence.
One practical note on headings: the editor exposes six levels, and that is more than most pages need. A document with Heading 4, Heading 5 and Heading 6 in the body usually means the outline was never planned. Two or three levels answer almost every case, and the extra levels are there for technical documents with deep nesting.
Where do alignment, indentation and font size fit?
These three controls change appearance inside a block and do not change the block type.
Alignment offers Left, Center, Right and Justify. Justify stretches a line to both margins. Use it for body text in a printed document, avoid it for short lines and captions, where the gaps between words become visible.
Indentation moves a block one step right or left. It works on paragraphs, headings and list items, and it is the control to reach for when a quotation needs visual offset without becoming a Quote block.
Font size applies to a selection, not to a block, and the palette has eight steps: 12, 14, 16, 18, 20, 24, 28 and 32 pixels. The default body size sits in the middle of that range. Two habits keep documents consistent: pick one size for body text and never change it mid-document, and reserve the largest steps for a title that sits outside the Heading structure.
There is also a symbol palette with grouped characters for currency signs, math operators, arrows, dashes and typographic quotes. Inserting a real en dash or a degree sign from the palette is safer than typing an approximation, since the character survives copy, export and paste into other applications.
Links go through a small dialog. Select the words, open Insert Link, paste the address, confirm. The linked text keeps its current marks, so a link inside a bold phrase stays bold.
How do tables, images, code and the outline work together?
A document that mixes prose, a table and a block of code needs all three to behave under export, and this is where a browser editor usually shows its limits.
Tables are inserted as a grid and edited with row and column actions: add a row below, delete a row, add a column to the right, delete a column. Cells accept the same marks as body text. For export, a table becomes a real HTML table in HTML and a pipe table in Markdown, so a comparison you build once can be pasted into a wiki or a CMS without being retyped.
Images are inserted by address or from a local file, then aligned inside the document. They are useful for a screenshot in a support note or a diagram in a specification, though a document meant for email is usually better kept text-only.
Code blocks are the reason many people open an editor at all. A fenced block in the export keeps its line breaks, and inline code inside a sentence keeps the monospace styling without breaking the paragraph.
The table of contents panel reads the heading structure and lists the sections in order. It updates as headings are added or removed, and clicking an entry moves the view. In a long document, this is faster than scrolling and it exposes a broken outline immediately: a section that never appears in the panel was typed as a paragraph, not as a heading.
Fullscreen hides the surrounding page and gives the document the whole window, which matters on a laptop screen when a table has six columns.
What does the character limit do, and when is it useful?
The Limit control opens a small panel with a switch and a number field. Turn the switch on, set a maximum, and the status row starts reporting the remaining budget next to the counters. The field accepts values from 50 upward, and typing a new number replaces the old one rather than appending to it.
The limit is a writing aid, not a hard wall. Nothing truncates your text silently. The value simply tells you how much room is left, counted in characters, which is the unit that submission forms, meta descriptions, product listings and abstracts actually enforce.
Two habits make the limit useful.
- Set the limit before writing, not after. Watching the remaining count fall from 300 to 40 changes how you phrase the last sentence.
- Keep the counter row visible. Characters, words, sentences, paragraphs and estimated reading time sit in the same line, so a text that fits the character limit but runs to eight paragraphs is visible as a shape problem, not just as a number.
The reading time estimate assumes a steady reading speed and rounds to the nearest minute. Treat it as a signal, not a promise: a page of dense technical prose reads slower than a page of dialogue at the same word count.
Which export format should you choose?
Six outputs are available, and the right one depends on where the document goes next.
| Format | Best for | Keeps structure | Editable later in |
|---|---|---|---|
| HTML | Web pages, CMS body fields, email templates | Yes, semantic tags | Any editor with source view |
| Markdown | READMEs, wikis, static sites, notes apps | Yes, headings and lists | Any plain text editor |
| DOCX | Word users, review cycles, formal delivery | Yes, styles approximated | Word, LibreOffice, Google Docs |
| TXT | Plain archives, form fields, scripts | No, characters only | Anything |
| JSON | Reopening the same document in this editor | Yes, full state | This editor |
| Paper, PDF through the browser dialog | Yes, as rendered | Not editable |
The JSON option deserves a note. It stores the editor's own document state, which is the only format that reopens with every mark, block and table exactly as it was. Keep the JSON next to the exported file when a document will be revised more than once: the HTML export is for the reader, the JSON is for the next editing session.
Copy is separate from export and offers two modes. Copy as plain text strips formatting and leaves characters, which is what you want for a chat message or a form field. Copy as rich HTML keeps formatting, which is what you want when pasting into an email client or a document app that understands markup.
Print opens the browser print dialog, where the destination can be a printer or a PDF file. This is the shortest path to a PDF that looks like the page, and it needs no extra library.
How do import and paste fit into the workflow?
Import accepts Markdown, HTML, DOCX and TXT files and loads them into the document. This turns the editor into a converter as well: open a Word file, fix the parts that did not survive, export as Markdown.
Pasting is the faster route for short material. Text pasted from a web page or another editor arrives with its formatting attached, and the marks that have a toolbar equivalent survive. Pasting from a word processor can bring styles that do not map onto the eight supported marks, so a paste, then a quick pass with Clear formatting on the affected paragraphs, is often cleaner than fixing the result line by line.
Clear formatting removes marks from a selection and leaves the block type alone. Clear document empties the document and the saved copy behind it, which is the control to use before handing the machine to someone else.
Is the document private, and what happens to it when the tab closes?
Everything runs in the browser. No formatting action, import or export sends the document anywhere, and there is no account to attach it to.
The editor saves the document to the browser's local storage as you type and restores it when you open the page again. That restore is the reason a document survives a reload, a crash, or a closed laptop lid. It also explains an occasional surprise: text from an earlier session reappears, and the first thought is that the tool inserted it. Clear document is the fix, and once cleared the saved copy is gone.
Because the save is local, the same document is not on another device, and a browser profile reset or a different browser window will not have it. Export the formats you need before clearing site data. Undo and redo cover the current session only.
Nothing in the interface asks for an email address, and nothing blocks the export behind a sign-up. That is a design choice: a formatting tool earns trust by being boring about data.
Frequently Asked Questions
Does the editor work offline?
After the page has loaded, formatting, counting and export run in the browser without a network request. A reload while offline cannot fetch the page itself, so keep the document exported if the connection is unreliable.
Why does my heading not appear in the table of contents?
The line is probably a paragraph with larger text rather than a real heading. Put the cursor in the line and check the block dropdown: it should read Heading 1, Heading 2 or Heading 3. Font size alone does not create structure.
What is the smallest character limit I can set?
Fifty characters. The field rejects lower values on confirm, which prevents a limit that is smaller than a single sentence.
Can I paste a table from a spreadsheet?
Cells arrive as text separated by tabs or newlines, and rebuilding the grid with the table controls takes a minute. For large data sets, export the sheet as HTML and import that file instead.
What happens if I open the same document in two tabs?
Each tab keeps its own document in memory, and the last one to save wins. Work in a single tab per document, and export before opening a second copy.
Is Markdown export lossless?
Headings, lists, links, quotes, code, tables and marks survive. Font size, alignment and colours do not, because Markdown has no syntax for them. If those matter, keep HTML or the JSON state.
Perpignan, France · SO reputation 19991 · Badges: 53🥇191🥈358🥉 · SO member since 2013