HTML is the markup of the web, with native headings and tables. TXT is plain text, with no markup of any kind. pandoc sits between the two, and this page says exactly what happens to an HTML file on the way to becoming a TXT one.
What runs when an HTML file becomes TXT
pandoc in two passes, on a machine we rent and watch. Your HTML file is uploaded once, pandoc runs once, the TXT comes back, and neither file is kept. HTML to TXT is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the HTML into the TXT
Lists from the HTML file, nesting included, plus code blocks, block quotes and links, all re-expressed in TXT.
Images: pandoc extracts them out of the HTML file into a working directory and re-embeds them in the TXT, so nothing ends up pointing at a file that no longer exists.
What HTML to TXT costs you
Tables. The TXT writer cannot carry one, and the probe caught this the hard way: a CSV file, which is nothing but a table, came back as a well formed and completely empty TXT with a zero return code. The engine now refuses that case outright rather than handing you the emptiness.
If a model is going to read the TXT
Structure is what survives from the HTML file, and structure is what a model needs. HTML in, TXT out, with the heading tree intact instead of flattened into one long paragraph.
HTML to TXT, measured rather than promised
Running HTML to TXT against the real engine with a real file, pandoc wrote 270 bytes of TXT in under a tenth of a second, machine otherwise idle. That is one HTML file on one day and not an average, which is why the number is given together with the file that produced it.
The HTML to TXT verdict was reached by reading the text back, meaning the output decodes as readable text and still carries the witness word, which is the only check a plain text target allows. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the TXT file has anything inside it.
The same HTML file, sent somewhere else
Other outputs the probe measured out of an HTML file, so the cost of choosing TXT can be read against something. Sizes do not compare across engines, because each family was probed with its own HTML witness file.
HTML to PDF: 25,178 bytes in 1.9 seconds, verified by a format signature.
HTML to MD: 371 bytes in under a tenth of a second, verified by a pandoc round trip.
HTML to DOCX: 10,277 bytes in 0.1 seconds, verified by a pandoc round trip.
HTML to EPUB: 5,027 bytes in 0.1 seconds, verified by a pandoc round trip.
HTML to RTF: 775 bytes in under a tenth of a second, verified by a pandoc round trip.
HTML to ODT: 7,629 bytes in 0.1 seconds, verified by a pandoc round trip.
Other ways into TXT, and what they measured
Among the published routes into TXT, HTML is the first largest output of the 11 measured. The witness files differ, so this ranks the probe run and not your document.
JSON to TXT: 264 bytes in under a tenth of a second.
MD to TXT: 264 bytes in under a tenth of a second.
MOBI to TXT: 219 bytes in 0.5 seconds.
ODT to TXT: 264 bytes in 0.1 seconds.
RTF to TXT: 263 bytes in under a tenth of a second.
What we will not pretend about HTML to TXT
An HTML file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An HTML to TXT run that passes 60 seconds is killed, and the pandoc process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
32 of the 935 pairs probed in the family that serves HTML to TXT failed, and this pair is not one of them. They fail for reasons worth knowing: a writer that cannot carry what the document is made of, or output the engine could not read back. They are counted here rather than hidden, because a pair that fails quietly is worse than one that fails loudly.
pandoc never writes the TXT through a TeX engine here, and it never writes PDF at all: the eleven engines it would need are not on this machine and a TeX distribution weighs several gigabytes. Anyone who wants a PDF out of an HTML file goes through LibreOffice or calibre, both of which genuinely can.
One HTML file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
HTML to TXT: what people ask
What actually converts my HTML file to TXT?
pandoc does it, in two passes, on a machine we rent and watch. Not a browser trick and not somebody else service: the HTML file is uploaded once, pandoc runs once, the TXT comes back, and neither file is kept afterwards.
How long does HTML to TXT take?
On the file the probe used, pandoc took under a tenth of a second and wrote 270 bytes of TXT. That is one real measurement on one real HTML file, not an average and not a promise about yours: a larger HTML takes longer, and past 60 seconds the run is stopped.
What do I lose going from HTML to TXT?
The one to know about first: Tables. The TXT writer cannot carry one, and the probe caught this the hard way: a CSV file, which is nothing but a table, came back as a well formed and completely empty TXT with a zero return code. The engine now refuses that case outright rather than handing you the emptiness.
Are the tables in my HTML file still tables in the TXT?
No, and that is a property of TXT rather than a defect of this path. TXT cannot hold a table, so an HTML file built around one is the wrong candidate for this pair.
Is HTML to TXT free?
There is a free allowance every month, and one HTML to TXT conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse TXT.