Convert TXT to PDF

The one question a txt to pdf converter has to answer

Plain text has no idea what a line is. Two files can hold identical sentences and disagree completely about where the newline characters sit, and neither of them is wrong. In the first, somebody — or their mail client, or a terminal, or a habit inherited from a machine with an eighty-column screen — ended every line by hand at around seventy characters. In the second, an entire section sits on a single line thousands of characters long, and the software that displayed it folded that line to fit whatever window it happened to be in.

Those two files must be treated differently, and almost nothing that turns text into a document bothers to look. Print the first as though each newline began a new paragraph and you get a column with a ragged left-hand edge and a fresh indent every six or seven words, which is unreadable in a way that is hard to name but immediately obvious. Refuse to re-flow the second and the sentences run straight off the right margin, or arrive at one line per page. Getting this backwards is the single most common reason a converted text file comes out looking broken.

So this page works it out before it lays anything down, and then tells you what it concluded and how sure it is. The test follows from what wrapping actually is: software that folds a paragraph fills each line until the next word will not fit. That means in a genuinely hand-wrapped file it holds for practically every line that the first word of the line beneath it would have overflowed. It is a definition rather than a correlation, so the proportion sits close to one. In a log, where line lengths are whatever the messages happened to be, plenty of short lines had room to spare and the proportion collapses. Whichever answer comes back, the two buttons above let you overrule it — detection with no control attached is just a quieter guess.

Text to PDF, when the text is not in a file yet

A good share of the people who need this never had a file to begin with. The material is sitting in a terminal window, a chat log, a notes app, a support ticket, an email nobody wants to forward. So the box for pasting stands beside the drop target as an equal, not hidden behind it, and it produces exactly the same document by exactly the same route.

There is one difference, and it is worth stating rather than papering over. A text area in a web browser rewrites Windows-style line endings to plain ones before any code on the page is allowed to see the content. That behavior is written into the HTML specification and cannot be worked around by anyone. Anything this tool might tell you about line endings or about how the material was wrapped would therefore be an invention for pasted text, so it says unknown instead and hands the wrapping decision to you. If that distinction matters to what you are doing, drop the file itself.

Three layouts that differ in more than a color

Formal is a report: inch margins, Times, a rule under a running header carrying the file name, and Page 3 of 12 centered at the foot. Lightopens the leading right up and puts noticeably fewer words on each sheet, which is what you want when the destination is a screen and nobody is going to print it. Compactpulls the margins in to half an inch, drops to nine and a half points and closes the gaps between paragraphs, on the theory that a four-hundred-page log becomes a different object at two hundred and forty.

Every one of those measurements is a starting point and none of them is a ceiling. Type size, margin, typeface, page numbers and the header are all separately adjustable afterwards, and adjusting one does not silently drag you back to a preset. The label simply reads adjusted until you press the template again on purpose.

What a plain text file quietly carries

Less than a word processor, more than nothing, and the difference matters. A blank line is a paragraph boundary — the one structural convention every reader of plain text agrees on. Leading spaces are meaning, not decoration: flatten them and a directory listing, a stack trace or an indented block of code stops being legible, so they survive as a measured indent rather than being swallowed. Tabs land on real tab stops, eight columns apart by default and adjustable when the file contains any, because a tab replaced by a single space slides an entire column out of alignment.

And the form feed, character twelve, still means what it has meant since line printers: the page ends here. Files exported from mainframes, accounting systems and older report generators are full of them, and every one becomes an actual page break rather than an invisible character that quietly vanishes.

Headings are the thing plain text genuinely cannot express, and guessing at them from capital letters produces confident, eighteen-point mistakes. The optional formatting step exists for that instead: it opens the same editing surface used bythe Markdown editor and runs the result through the same layout code as Markdown to PDF, so a heading you add here is identical to a heading added there. Going the other direction — pulling words back out of a finished document — is a genuinely harder problem and lives atPDF to text.

Encoding, and why your file may be full of å

A file extension of .txt tells you nothing at all about which bytes stand for which characters. Text saved out of Notepad on a Western European Windows machine is very often Windows-1252; text out of a modern editor is UTF-8; text out of PowerShell is frequently UTF-16 with a byte order mark at the front. Read one as another and every accented letter turns into a small pile of punctuation. The bytes are examined here before anything is laid out, the answer is displayed, and it can be overridden — necessary because a Latin-1 file can be perfectly valid UTF-8 as well, and in that case only a human looking at the words can tell which reading is the right one. The wider subject is covered inUTF-8 versus ASCII.

Nothing is uploaded, including the very large ones

No route on this site accepts a document from this page. The bytes are decoded, measured, paginated and assembled into a PDF by code running in the tab you have open, and the download button points at something that never existed outside your own memory. The method for checking that claim yourself, rather than believing it, is written up inhow to verify a tool runs locally.

Size is not a reason to be turned away either. A twenty megabyte server log is a thing people genuinely have, and it becomes thousands of pages, so the work is done in slices with the browser handed back control between each one and a counter that reports pages actually finished rather than a bar that guesses. What you get beforehand is an honest warning about what the job will cost your machine, followed by the job.