Help with Text to PDF
Fonts supported by Text to PDF
Choose a font in Text to PDF and select Preview PDF. The tool checks your text for missing characters before creating the document. This page explains warnings, fonts left out of the picker and how to check the finished PDF.
Open Text to PDF →If a character is missing
A font can support ordinary letters but lack an accent, symbol or character in a name. Text to PDF lists the unsupported characters when you choose Preview PDF.
- Paste your complete text into Text to PDF, choose a font and select Preview PDF.
- If a missing-character warning appears, choose another font and preview again. Keep the names, accents and symbols your document needs.
- If the warning says the document needs complex-script or right-to-left layout, use an editor that supports that writing system. Changing the font alone will not add that layout support.
Why a font may be missing from the picker
Text to PDF offers only the bundled font files that passed our embedding and text-extraction checks. Some fonts available in our graphic tools are left out of this document tool. Uploaded fonts are not supported here.
Fonts excluded from Text to PDF
These results apply to the exact files bundled here. Another version or weight may behave differently.
| Font | Why it is excluded |
|---|---|
| Aboreto | Copied text did not match the test sample. |
| Bahiana | Copied text did not match the test sample. |
| Barrio | Copied text did not match the test sample. |
| Bytesized | Copied text did not match the test sample. |
| Castoro Titling | Copied text did not match the test sample. |
| Gulzar | The font could not complete the PDF embedding test. |
| KoHo | Copied text did not match the test sample. |
| Noto Sans Mongolian | The font could not complete the PDF embedding test. |
| Paprika | Copied text did not match the test sample. |
| Sedan SC | Copied text did not match the test sample. |
| Spectral SC | Copied text did not match the test sample. |
Check the finished PDF
A successful preview means the document was created. Check the downloaded file before sharing it:
- Open it in the PDF app your recipient will use. Review every page, especially names, accents, symbols and line breaks.
- Copy a sentence into a text editor and compare it with the original, including its accents and punctuation.
- If the document will be printed, test one page at the intended size.
Make and preview your document in Text to PDF.
Test method and font-file results
1024 of 1035 font files passed. The remaining 11 files are excluded from the Text to PDF picker. A failure here does not mean a font is unsuitable for PNG graphics or vector outlines.
Find a font-file result
What we test
- Check that the font contains A–Z, a–z, digits, spaces and the punctuation . , ! ? -. Add selected accented Latin, Greek and Cyrillic characters only when that font contains them.
- Embed a subset of the font in a new PDF, with ligatures disabled, and write the samples at 16 pt. Reject missing basic characters, invalid metrics and embedding errors.
- Open the PDF with the same PDF.js reader in Chromium and WebKit. Compare extracted text with the source after removing whitespace. Both engines must return the expected characters.
- Render the page in both engines and require visible ink. This detects blank output; it is not a visual assessment of every glyph or a test of reading quality.
Each result records the font file hash. The report also records the catalogue and PDF-library hashes, so changed files can be identified and tested again.
Audit snapshot and software
Audit run (UTC):
- chromium: 148.0.7778.96
- webkit: 26.4
pdf-lib 1.17.1 · fontkit 1.1.1 · PDF.js 6.3.289
Report fingerprint (SHA-256): 096104e108072d7f5d99311451ac9e3a424f3aacb617853761394345fa6afe0d
Results and samples
Download the complete results to see every font file, its pass/fail result, the exact characters tested and any recorded failure. The CSV uses stable English column names and preserves diagnostic messages verbatim.
The sample PDF uses the same embedding settings and character sample as the audit. Try selecting and copying its text in your own PDF reader. This checks that sample only, not every document or character you might use.
Characters checked in the Lato sample
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789 .,!?-ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæçèéêëìíîïñòóôõöøùúûüýÿŒœŁłŠšŽžı—–€£
What the audit does not cover
- A pass applies to this exact font file, sample and export pipeline. It does not certify the entire font family, every Unicode character or every language.
- Greek and Cyrillic checks use a small selection of characters, not complete alphabets. Complex-script shaping, right-to-left paragraphs, emoji, variable fonts and all OpenType features are outside this audit.
- WebKit and Chromium run the same PDF.js reader here. They do not stand in for native Safari, Preview, Acrobat, mobile download handling or physical printers.
- Text extraction and visible ink do not establish correct reading order, accessible PDF tagging, PDF/A compliance, attractive typography or successful printing.
- The audit is for searchable Text to PDF exports. PNGs, outlined SVGs, printable-letter PDFs and raster design PDFs use different workflows; their lettering is not selectable document text.