Text to PDF
Converting locally — nothing is uploaded
Notes, READMEs and markup set as proper documents — real type, real margins, real pages.
Drop a text file on the table
or — nothing leaves this tab
TXT · MD · HTML
From plain to pressed
A .txt file is words without a body; a README.md is structure without paper. This pass gives both the finish they were missing: your text flows into a typeset page at reading size with proper leading, Markdown structure becomes visible hierarchy, and the result runs through your own print engine as selectable, searchable vector PDF.
Meeting notes to hand out, a manuscript chapter an agent asked for “as a PDF”, a chat log that has to survive legal review — set once here, then archive or send. If the deliverable is physical, the press directory takes over from there.
Questions people ask
Which file types does this cover?
Plain text (.txt), Markdown (.md/.markdown) and raw HTML (.html/.htm). Plain text keeps its line breaks as paragraphs; Markdown renders with headings, lists, links, code blocks and tables; HTML is taken as-is, minus scripts.
Why not just print the text file directly?
You could — but your browser will set it in tiny monospace with default margins and no paragraph spacing. Here it’s set like a document: serif body text at reading size, real paragraph flow, sane page breaks. The difference is one page vs four.
How is my Markdown rendered?
Through a standard CommonMark renderer before typesetting: # headings become section titles, - lists become bullet lists, `code` becomes monospace, tables and blockquotes carry through. GitHub-flavoured extras like task lists are simplified to their text.
Is my HTML sanitized?
Scripts and inline event handlers are stripped so the preview iframe stays inert. Since everything runs locally anyway, this is hygiene rather than protection — the file never leaves your machine either way.