Tools
Data & text tools
Convert Markdown, HTML, JSON, XML, and plain text into the documents and data formats you actually need to hand over — free and in the browser.
Start here
- Convert
Markdown to Anything
Export Markdown to PDF, Word, HTML, or Text with formatting intact.
MARKDOWNANYTHING - Convert
HTML to PDF
A paginated PDF from an HTML file — links and headings kept.
HTMLPDF - Convert
JSON to CSV
Array of objects to a spreadsheet-ready CSV.
JSONCSV - Convert
XML to JSON
XML converted to JSON with attributes and nesting kept.
XMLJSON - Convert
EPUB to PDF
DRM-free eBooks laid out on fixed pages.
EPUBPDF - Convert
HTML to Word
HTML tables, lists and headings as a real Word document.
HTMLWORD
All Data tools by task
Which document tool do you need?
Match the source you have to the output someone is asking for:
| What you need to do | Use this tool |
|---|---|
| A README or notes must become a PDF, Word file or web page | Markdown to Anything |
| A web page or invoice needs to be a fixed document | HTML to PDF |
| HTML content needs to be editable in Word | HTML to Word |
| Plain text needs to become a proper PDF | Text to PDF |
| I need to hand JSON to someone as a document | JSON to PDF |
| API data needs to open in a spreadsheet | JSON to CSV |
| Legacy XML needs to become usable JSON | XML to JSON |
Why Markdown and HTML need converting at all
Markdown is written to be readable as plain text and rendered later, which makes it excellent for documentation and useless as a deliverable. Nobody accepts a .md file as an assignment, a report, or a client hand-off. Converting to PDF applies real typography — headings, spacing, monospaced code blocks, working tables — and produces something that opens identically everywhere.
HTML has the opposite problem: it renders everywhere but is not fixed anywhere. The same invoice or certificate reflows by viewport, and a browser's own print dialogue adds headers, footers, and page numbers you did not ask for. Converting to PDF pins the layout and drops the browser chrome, which is why it is the standard step for generated invoices, receipts, and certificates.
JSON to CSV is the same mismatch in data form. JSON is hierarchical and nests arbitrarily; a spreadsheet is a flat grid. The conversion walks the structure and flattens nested keys into columns, so an API response becomes something a non-technical colleague can open in Excel or Sheets without touching a parser.
Document and web tools FAQ
Are Markdown tables, code blocks, and links preserved?
Yes. Standard Markdown plus common GitHub-flavoured extensions are parsed, so tables render as tables, fenced code keeps its monospaced formatting, and links stay clickable in the PDF.
Does HTML to PDF include the CSS styling?
Yes. The page is rendered with its stylesheet applied, so layout, fonts, and colours match what a browser shows — without the print headers and footers a browser adds.
How is nested JSON handled when converting to CSV?
Nested objects are flattened into dot-notation column headers and arrays are expanded into rows, giving a predictable flat table rather than raw JSON dumped into one cell.
Can I paste content instead of uploading a file?
Not at the moment — each tool takes a file. Save your Markdown, HTML, JSON or XML as a file first; every text editor can do that.
Is my code or data sent anywhere else?
No. Browser-based tools never upload the file at all; server-based ones delete the upload and the result one hour after processing. Nothing is read by people, logged beyond standard request logs, or used for training.
Looking for something else? Search all tools.