Choose A4 or US Letter dimensions with Standard 14 PDF Type 1 fonts
Sharing meeting notes, technical README files, or plain .txt logs often requires turning raw text into a fixed-layout PDF that looks identical on every screen. Instead of pasting drafts into a word processor, you can paginate plain text or Markdown straight inside your browser using built-in Standard 14 PDF Type 1 fonts.
Choosing A4 vs. US Letter page size and margins
In Page size, A4 creates 595.28 by 841.89 pt sheets, while US Letter creates 612 by 792 pt sheets. The tool automatically defaults to US Letter when your browser locale is US, Canadian, or Mexican, and defaults to A4 elsewhere.
Every page applies a uniform 56 pt margin on all four sides, leaving clean whitespace for binding or printing. Under the Library of Congress PDF 1.7 (ISO 32000-1) format description, default user-space coordinates measure 72 pt per inch and allow word wrapping and page pagination calculations without external layout engines.
Selecting Sans, Serif, or Mono fonts and text sizes
Under Font, Sans maps to PDF Standard Helvetica, Serif maps to Times-Roman, and Mono maps to Courier. Text size lets you pick Small (10 pt), Medium (11 pt), or Large (13 pt) with 1.4x line spacing.
Because Standard 14 Type 1 fonts are built into every compliant PDF viewer, the generated PDF needs zero embedded font binaries and stays tiny. If you need to pull plain text back out of an existing PDF later, you can extract plain text back out of any PDF.
Which Markdown elements render automatically in the PDF?
Checking Format Markdown converts block-level syntax such as headings, lists, blockquotes, fenced code blocks, horizontal rules, and pipe tables into structured PDF blocks. Unchecking it treats every line as literal plain text with manual line breaks preserved.
| Markdown syntax | PDF rendering behavior | Font & spacing details |
|---|---|---|
# to ###### headings |
Scaled bold section titles | 2x down to 1x base text size |
-, *, 1. lists |
Indented bullet or numbered items | Up to 3 nested indent levels |
- [ ] and - [x] |
Task list checkboxes | Rendered as [ ] and [x] |
> blockquotes |
Indented quote block | Vertical rule + muted grey text |
``` code fences |
Monospace code block | Courier at 0.9x size on tinted box |
--- horizontal rules |
Full-width divider line | Clean horizontal stroke across margin |
Opening a .md or .markdown file enables Format Markdown automatically, and pasting text with # headings or - bullets turns it on too. Block parsing follows the core structure of the CommonMark 0.31.2 Markdown specification for predictable line wrapping.
For workflows centered exclusively on rich Markdown styling, you can also open the dedicated Markdown-to-PDF formatter. Both tools run locally in your browser with zero server round-trips.
Vector PDF typography vs. headless browser printing for code and tables
Long paragraphs wrap automatically at word boundaries to fit inside the printable width, and overly long URLs or unbroken tokens wrap character by character so nothing overflows the right margin. Direct vector PDF typography avoids the heavy memory overhead of headless browser printing while keeping headings paired with following text.
Rendering GFM pipe tables, task lists, and Courier code snippets
Pipe-delimited tables from the GitHub Flavored Markdown (GFM) specification render as bordered grid cells with a shaded header row. Column widths distribute evenly across the available content width, wrapping multi-word cell text cleanly onto additional lines.
Task lists support up to 3 levels of indentation using two-space steps, making project checklists easy to scan on paper. Fenced code blocks typeset monospace Courier code snippets at 0.9x size inside a shaded box with clean vertical breathing room.
Why inline bold, italic, and link URLs become plain text
Inside paragraphs, inline **bold**, *italic*, `code`, and ~~strikethrough~~ markers are stripped so raw punctuation does not appear in printed prose. Markdown hyperlinks convert to label (url) so printed readers can still see the full destination address.
If you need full CSS typography, custom web fonts, or inline bold/italic spans inside paragraphs, you can render full CSS styling and web layouts as PDF instead.
Why do emoji or non-Latin characters turn into question marks?
Emoji and non-Latin scripts turn into question marks because PDF Standard 14 fonts use WinAnsiEncoding, which covers Western European Latin characters only. Before drawing each line, the text cleaner replaces unsupported Unicode code points with ? so the PDF builder never crashes.
Understanding WinAnsiEncoding limits in Standard 14 fonts
Standard Helvetica, Times-Roman, and Courier include roughly 200+ Western European glyphs mapped to WinAnsiEncoding (Windows-1252). Whenever emoji, Cyrillic, Arabic, or East Asian characters appear in your draft, the result panel reports the exact count of replaced glyphs.
Tip: Put a
# Titleheading on the first line when pasting notes directly into the editor. The builder uses that heading automatically as the downloaded PDF filename instead of genericDocument.pdf.
Working within the 5 MB file limit and automatic naming
You can drag and drop or open Markdown and .txt files up to 5 MB (5,000,000 bytes) directly from disk, which protects browser memory from accidental binary uploads. Larger log archives should be trimmed before loading so pagination remains responsive.
For structured spreadsheet exports rather than prose notes, you can turn comma-separated spreadsheets into PDF tables with automatic column alignment.