Convert a Webpage to PDF with Embedded Fonts in Firefox
Save a webpage as a PDF in Firefox, then check font embedding, page layout, and searchable text before you rely on the file.
Short answer: In Firefox, open Menu → Print…, choose Save to PDF as the destination, inspect the print preview, and save. Firefox’s documented workflow does not guarantee that every webpage font will be embedded. If embedding is a requirement, inspect the saved PDF with a PDF reader or font-inspection tool; do not infer embedding from how the page looks.
Font embedding, visual fidelity, and text extraction are separate checks. A PDF can look correct while its fonts are not embedded, or while some text cannot be selected, searched, or extracted as expected.
Save a webpage as a PDF in Firefox
- Open the webpage in Firefox and select Menu → Print… (or use your operating system’s print command).
- In the print dialog, set the destination to Save to PDF.
- Review the preview. Webpages can be designed to look different on paper, so use the preview to judge the page breaks and layout.
- Set the options you need, such as orientation, pages, color, paper size, scale, margins, headers and footers, and print backgrounds. Available controls can vary by platform or destination.
- Select Print, choose a file name and location, and save the PDF.
- Open the saved file and verify font embedding if it is a strict requirement. Also check visual appearance and selectable or searchable text separately.
What “embedded fonts” means
A PDF with an embedded font contains font data in the document so a PDF viewer can render text without relying solely on the reader’s installed copy of that font. Seeing the expected typeface on your screen is not enough to prove embedding: a viewer may substitute a local font, or the PDF may render acceptably for other reasons.
Check the document’s font properties in a PDF reader or use a PDF font-inspection utility. Look for each relevant font and whether it is marked embedded or embedded as a subset. If text extraction matters, select and copy representative text or search for it as a separate check. These checks address different properties; passing one does not prove the others.
Print settings that affect the result
| Setting | What to check |
|---|---|
| Destination | Choose Firefox’s Save to PDF destination. A platform PDF printer is another route, but the available behavior can differ. |
| Paper size and orientation | Match the intended page format. A mismatch can change line wrapping and page breaks. |
| Scale and margins | Use the preview to catch clipped content, unexpectedly small text, or unwanted whitespace. |
| Pages | Confirm the page range and total pages before saving, especially for long pages. |
| Backgrounds and color | Enable print backgrounds when the design depends on background colors or images. Check that text remains legible. |
| Headers and footers | Review whether page numbers, titles, dates, or URLs should appear in the saved document. |
Not every setting appears on every operating system or for every destination. If an option is missing, the print route or platform may not expose it.
Verify fonts and text in the PDF
- Check the font list: Open the PDF’s document properties or font inspection view and confirm the fonts used by the page are listed as embedded or embedded subsets.
- Check appearance: Review pages containing distinctive typography, symbols, or non-Latin text at normal and enlarged zoom. Compare them with the browser page where practical.
- Check text behavior: Select, copy, and search for representative text. If the PDF is intended for downstream processing, test extraction with the actual tool or workflow that will consume it.
- Check links and page structure if needed: Inspect hyperlinks and page breaks. Printing may not preserve every on-screen interaction or layout detail.
- Keep the verified output: If the file is a deliverable, retain the PDF you inspected rather than regenerating it later with potentially different settings.
There is no documented universal guarantee here that Firefox’s built-in export embeds every font in every webpage. When the result fails a required check, compare another available route—such as the operating system’s PDF printer or a dedicated PDF export extension—and inspect that output too. No route is established as a universal fix.
Alternatives and their tradeoffs
| Route | When it may fit | What to verify |
|---|---|---|
| Firefox Save to PDF | Convenient built-in export for a page already open in Firefox. | Font embedding, layout, text selection/search, links, and page breaks in the result. |
| Platform-provided PDF printer | Useful to compare when the built-in route gives an unsuitable output or lacks a needed control. | The resulting file’s fonts and text behavior. A different printer is not a guaranteed font fix. |
| PDF-export extension | May offer a workflow or controls that suit a particular use case. | Output properties, extension permissions, trustworthiness, availability for your platform, and whether it preserves links and selectable text. |
The sources establish Firefox’s built-in workflow, but do not establish a head-to-head winner among these routes. Choose based on the PDF you produce and verify, rather than assuming a route guarantees embedding.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| The PDF looks right, but a font is not marked embedded. | Visual rendering and embedded font data are different properties. | Use the output only if embedding is not required. Otherwise compare another export route and inspect its font list. |
| Text looks broken or changes after saving. | A particular font, platform, or Firefox version may have a print-related issue. | Confirm the affected font and platform, update Firefox where appropriate, and compare another route. Treat reports about specific configurations as specific; they do not establish a universal failure. |
| Characters look correct but search or extraction is wrong. | Text mapping or extraction can fail independently of font embedding and visual appearance. Ligature mapping issues have been reported separately from font embedding. | Test search and copy/paste in the PDF. If downstream extraction is essential, test with that exact consumer and compare another export route. |
| Content is clipped, tiny, or split awkwardly. | Paper size, scale, margins, orientation, or the webpage’s print layout may not fit the page. | Adjust those controls and inspect the preview again before saving. |
| Background colors or graphics are missing. | Print backgrounds may be disabled or unavailable in the selected route. | Check the print settings for a background option. If unavailable, compare another route and inspect the PDF. |
| A setting shown in a guide is missing. | Print controls vary with operating system and destination. | Check the options exposed by your current dialog or try another available PDF destination. |
Mozilla Bugzilla contains reports about particular Firefox and system configurations, including a historical report involving downloadable fonts and third-party PDF printer software, and a later report about a system font on Linux. Those reports are evidence of specific edge cases, not proof that all Firefox PDF exports fail or that another route fixes every case.
Reliability, performance, and cost
For a one-off page, the built-in print workflow avoids setting up an automation service or installing an extension. The main reliability concern for this title is whether the saved artifact meets the font, appearance, and text requirements; verify those properties on the actual PDF. Long pages and complex print layouts may require preview adjustments, and the time to produce the file depends on the page and local environment. The research does not establish comparative speed or cost figures for the export routes.
If you need to capture webpages programmatically as images or PDFs, ScreenshotNeo is a website screenshot API and MCP server for developers. It provides PDF capture settings including paper size, margins, landscape, and page ranges. A screenshot-to-PDF workflow is not a substitute for verifying embedded fonts: inspect the resulting PDF when font embedding is a hard requirement.
Or skip the browser setup
For an API-generated PDF, use ScreenshotNeo’s API documentation. The following cURL request captures a webpage as PDF:
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-d format=pdf \
-o page.pdf
Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up free for 1,000 screenshots a month, with no card required.
FAQ
Does Firefox guarantee that Save to PDF embeds every webpage font?
No such guarantee is established by Mozilla’s documented save-to-PDF instructions. Inspect the saved PDF if embedding matters.
Can a PDF look correct without embedded fonts?
Yes. Appearance on one system does not establish that font data is embedded. Check font properties separately.
Does embedded font data guarantee searchable text?
No. Font embedding and text mapping or extraction are separate. Test selection and search in the file.
Will a PDF printer or extension fix a font issue?
It may produce a different result, but the available evidence does not show that any alternate route is a universal fix. Inspect each output against your requirements.


