How to Convert HTML to PDF with Adobe Acrobat

Direct answer: In Acrobat desktop, choose Create → Web page, enter a URL or browse to an HTML file, adjust capture and conversion settings if needed, then select Create. For one page that is already open in a browser, use the Adobe PDF toolbar’s Convert to PDF command, then name and save the file.

Acrobat lists HTML as a supported source format. The final PDF can span several standard-size pages, and the result depends on the page’s content and the settings you select.

Choose the right Acrobat workflow

Use case	Best workflow	Why
One page already open	Browser extension	Fastest path: convert the current page and save it.
URL or local HTML file	Acrobat desktop	Lets you enter a URL, browse to a file, and change conversion settings.
Several linked pages	Acrobat desktop site capture	Supports capture levels, entire-site capture, and path/server limits.
Simple personal copy	Browser Print → Save as PDF	Requires no Acrobat conversion settings, but does not provide the same site-capture and tagging controls.

Convert a URL or local HTML file in Acrobat desktop

Open Acrobat and select Create from the global toolbar.
Choose Web page in the left rail.
Enter the page URL, or choose the option to browse to an .html file.
For a single page, leave multi-level capture disabled. For linked content, select Capture multiple levels and specify the number of levels.
To request broad coverage, choose Get entire site. Use Stay on same path or Stay on same server to constrain what Acrobat follows.
Open Advanced settings when you need to control HTML conversion, images, colors, headers, page geometry, tags, or bookmarks.
Select Create, choose a destination, and review the generated PDF.

Acrobat can queue additional pages while a conversion is in progress. A multi-level capture follows links according to the level and scope rules you selected; it does not automatically guarantee that every page on a site is included.

Capture scope examples

One page: enter the exact URL and do not enable multiple levels.
Section of a site: enable multiple levels and select Stay on same path.
Several sections on one domain: use Stay on same server, then set a conservative level count.
Whole site: select Get entire site, but expect a larger job and inspect the output for navigation loops or pages that require login.

Convert the open page with the Acrobat browser extension

Open the page in your browser.
Select Convert to PDF in the Adobe PDF toolbar.
Choose a filename and save location.
Open the PDF and check page breaks, images, links, and any interactive content you expected to preserve.

The extension is suited to a single open page. Use the desktop application when you need multiple levels, whole-site capture, local HTML selection, or the advanced conversion controls described below.

Settings that control the PDF

HTML, fonts, and colors

Encoding: choose the character encoding when text displays with incorrect symbols.
Script fonts and sizes: adjust the conversion fonts when the source uses uncommon or missing typefaces.
Text, background, and link colors: preserve the source palette or choose readable replacements.
Force color settings across pages: use this when a multi-page capture needs consistent color treatment.

Images, backgrounds, and multimedia

Choose whether to include images.
Preserve page backgrounds when the background is part of the document’s meaning or layout.
Choose whether links are underlined.
Expand scrollable blocks when hidden content inside a fixed-height region must appear in the PDF.
When possible, embed or link multimedia according to the destination’s needs. Review the output because a PDF is not a full replacement for an interactive web application.

Tags, bookmarks, headers, and footers

Create PDF Tags: stores structure information corresponding to the source HTML.
Bookmarks: create navigational entries from available page structure when supported.
Headers and footers: add page titles or URLs to make printed or shared copies easier to identify.

Tags can help Acrobat build a more structured document, but selecting the option does not by itself prove that every generated PDF meets every accessibility requirement. Review heading order, reading order, link names, contrast, and form behavior when accessibility is important.

Page size, orientation, margins, and scale

Select a standard paper size for the audience that will print or archive the PDF.
Use portrait for text-heavy pages and landscape for wide tables or dashboards.
Set margins that leave enough printable space without shrinking the content unnecessarily.
Use scale-to-fit when content is clipped, then inspect small text at normal zoom.
Enable landscape switching when different pages need different orientations and the option is available in your conversion dialog.

How to handle common HTML sources

Public web pages

Enter the canonical URL and let the page finish loading before conversion when using the browser extension. For pages that depend on client-side scripts, verify the PDF rather than assuming that every dynamic region rendered.

Local files

Use Acrobat desktop’s browse control to select the HTML file. Keep related CSS, images, and fonts available at the paths referenced by the document. If assets use absolute web URLs, the conversion environment may need network access to retrieve them.

Pages with long feeds or scrollable panels

Use the option to expand scrollable blocks when the content inside a fixed-height element is required. Otherwise, the PDF may contain only the initially visible portion.

Acrobat’s documented flow does not establish that authenticated, session-bound pages will always convert. If the page needs a login, test the exact workflow and confirm that private content is not omitted or exposed through an unintended URL.

Search for several distinctive strings from the source page.
Check that headings and bookmarks follow a sensible order.
Open links and confirm that URLs point to the intended destinations.
Inspect images at 100% zoom for missing assets or unexpected blur.
Check every page for clipped columns, orphaned headings, blank pages, and awkward breaks.
Review headers, footers, page numbers, and source URLs.
If accessibility matters, inspect tags and reading order with Acrobat’s accessibility tools.
For multi-page or whole-site captures, confirm that the intended levels and scope were used.

Troubleshooting Acrobat HTML-to-PDF conversion

Symptom	Likely cause	Fix
Text shows as symbols	Wrong HTML encoding or unavailable font	Choose the source encoding and adjust script fonts in Advanced settings.
Images are missing	Images are excluded, blocked, or referenced by unavailable paths	Enable image inclusion and verify that local or remote asset paths are reachable.
Background colors disappear	Background preservation is disabled	Enable page backgrounds or choose a deliberate replacement color.
Only part of a scrollable panel appears	The panel remains fixed-height during conversion	Enable expansion of scrollable blocks, then inspect for duplicate or excessive content.
Wide tables are clipped	Portrait paper, narrow margins, or scale too large	Use landscape, reduce margins, or enable scale-to-fit.
Too many pages are captured	Capture level is too high or scope is too broad	Lower the level count and use Stay on same path or Stay on same server.
Linked pages are missing	Capture multiple levels is disabled or links leave the allowed scope	Enable multiple levels and review the path/server restrictions.
Interactive media does not behave like the site	PDF conversion cannot reproduce every web interaction	Use a static fallback, link back to the source, and verify multimedia handling.
PDF has poor accessibility structure	Tags were not created or source structure is ambiguous	Enable Create PDF Tags and review the generated structure manually.
Browser toolbar command is unavailable	Extension is not installed, enabled, or supported in the current setup	Use Acrobat desktop’s Create → Web page workflow and check Adobe’s current extension guidance.

Performance, reliability, and cost considerations

Keep scope deliberate: whole-site capture creates more work and more opportunities for unwanted pages, loops, or blocked content.
Start with a small level count: increase it only after the first PDF contains the pages you need.
Queue work: Acrobat can queue additional pages while a conversion is running, which is useful for a planned batch.
Expect source-dependent results: HTML is a supported format, but scripts, authentication, external assets, and unusual layouts can change the output.
Review before distribution: a successful conversion dialog does not guarantee correct pagination, complete assets, or accessibility.
Choose the simplest tool that fits: browser Print → Save as PDF is adequate for a basic copy; Acrobat is the better choice when capture scope and conversion settings matter.

Or skip the browser setup

ScreenshotNeo provides a website capture API and MCP server. One GET request can return a clean PNG, JPEG, WebP, or PDF; its capture options include full-page output, element selection, custom CSS and JavaScript, waits, headers, cookies, user agents, geolocation, PDF paper settings, margins, orientation, and page ranges. See the ScreenshotNeo documentation for the current parameters.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. An MCP server lets AI agents such as Claude and Cursor take screenshots. The Free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 shots. Sign up free for ScreenshotNeo.

FAQ

Can Acrobat convert an HTML file without hosting it?

Yes. In Acrobat desktop, choose Create → Web page and browse to the local HTML file. Keep referenced local assets available.

Will one web page always produce one PDF page?

No. Acrobat may split a web page across multiple standard-size PDF pages.

What does Create PDF Tags do?

It stores structure information corresponding to the source HTML and can support tagged navigation, but the result should still be reviewed for accessibility.

How do I capture several pages?

Use Acrobat desktop, enable Capture multiple levels, set the level count, and constrain links with Stay on same path or Stay on same server.

Is browser Print → Save as PDF equivalent to Acrobat site capture?

No. Printing is a simple alternative. Acrobat provides documented capture scope and HTML conversion settings that printing does not provide.