Draft persistence is explicit, not assumed
The editor remains unsaved by default. You can opt in to a device-local draft, save it immediately, or clear it without implying cloud backup.
Write or paste text in a local line-number editor with copy and download actions.
Notes and files stay in this browser unless you explicitly copy, print, or download them. Browser storage can be cleared by private mode, site-data cleanup, or browser settings, so export important notes.
The editor remains unsaved by default. You can opt in to a device-local draft, save it immediately, or clear it without implying cloud backup.
Use the tool first, then apply these checks to verify the inputs, interpret the result, and hand it off without displacing the primary workflow.
The gutter is a visual index for the current text. Copying or downloading should preserve only the editor text unless you intentionally need numbered output. When sharing review notes, state whether line references apply to this exact revision because edits can shift every later line.
Browsers commonly normalize editing to line-feed characters, while some systems expect CRLF or another exact byte representation. If the text will feed a compiler, patch, checksum or protocol that cares about bytes, verify the downloaded file in the destination tool rather than assuming visual lines preserve original encoding.
A line-number text area is useful for plain notes, logs, snippets and quick review. It does not replace syntax validation, code folding, multi-file search, structured diffs or language-aware refactoring. Move to the appropriate developer tool when the task depends on those semantics.
Copy and download actions create an explicit handoff. A browser tab can be closed, refreshed, suspended or cleared, and local persistence rules vary by tool. For material you cannot recreate, save a named file and verify that the downloaded text opens correctly before discarding the original source.