Browser extension — save the current webpage as PDF

Use Webpage to PDF's Quick, Custom, and Visual extension modes, review PDFs in the side panel, export selected elements, and handle debugger warnings and display recovery.

A webpage can open perfectly in your browser while a cloud conversion returns only its sign-in screen. The cloud browser does not have your signed-in session. Local conversion through the extension works on your current tab, so it can start with the content you have already opened.

The extension is now available on the Chrome Web Store. Install it, open the webpage you want to save, complete any sign-in or verification, then click the extension icon and choose Quick, Custom, or Visual to export a PDF.

Choose cloud or local conversion

Content to saveSuggested starting pointWhat to expect
Public articles and product pagesCloud conversion on the websiteNo extension required; a remote browser opens the URL independently.
A page you have already signed in to viewLocal extension conversionSign in and expand the content yourself first. The extension does not log in for you or bypass verification.
An open local development pageLocal extension conversionYour current browser must be able to reach its HTTP/HTTPS address.
A single component or article sectionVisual in the extensionSelect its container, then export the selected node.

Conversion creates a file; it does not submit your edits to the source website. Your right to save or share the content still depends on your access and usage permissions.

Start from the browser toolbar

  1. Open the page and wait for its main content. Sign in, expand collapsed sections, or complete the website's verification yourself if needed.
  2. Select the Webpage to PDF toolbar icon. Check that the title and domain match the page you intend to save.
  3. Choose Quick convert, Custom, or Visual. Quick and Custom started from the toolbar show progress and results in the browser side panel.
  4. Wait for the file to finish, check the first and last sections, page breaks, and images in the PDF preview, then download it.

Ordinary HTTP/HTTPS webpages are the supported starting point. Browser settings pages, extension pages, and file:// files are not supported conversion entry points. Some browser-protected pages may also prevent extension access even when they have a web address.

What each mode produces

ModeHow it worksBest use
QuickCaptures the rendered page in tiles and places them on a single PDF pageA continuous capture that preserves appearance. Text is generally not selectable and links are not clickable.
CustomGenerates a browser PDF using your paper and layout settings, then applies headers, watermarks, and other document optionsPaginated documents for reading, printing, and sharing.
VisualLets you edit the current page before exporting with Visual's settingsHiding an element, changing spacing, or saving one selected region.

Quick and Custom do not require an editing session. Visual requires signing in through the extension's Account tab and having Pro or the appropriate extension access. Access to cloud Visual with a free website account does not itself grant access to Visual in the extension.

The side panel's three states

Home identifies the current webpage and offers the three conversion modes. Its thumbnail helps you recognize the source; it is not the final PDF and does not update continuously. Settings at the bottom opens conversion options, while Account shows sign-in and access details.

Editing is the Visual workspace. The actual webpage remains on the left; the side panel contains node details, styles, the DOM tree, and change history. Check the selection outline before hiding or restyling an element. If you selected a small child element, choose its parent container in the DOM tree.

Results shows conversion progress, an error, or the finished file. Back to home is unavailable while a task is running, so another conversion cannot start through that button. A visible preview does not mean the file is ready: PDF generation and document processing may still be running.

Avoid refreshing, navigating, or closing the source tab during editing or conversion. A page change invalidates the content the task was using; the panel may return to Home and require a fresh start. To cancel an export, use the panel's cancellation control so the extension can attempt to restore the page.

Why Visual changes the webpage width

Before opening Visual, select Visual in Settings and check the viewport, Screen/Print mode, and other page options. The editor prepares the current page using that configuration. A narrow layout is expected when you selected a mobile viewport.

The default editor lives in the browser side panel, outside the emulated page. Extension preferences also offer an in-page panel. This changes where Visual appears; it does not provide full side-panel support in a browser that lacks it.

Print applies the website's own print CSS. Missing navigation, different colors, or a much plainer page may all come from that stylesheet. Choose Screen to retain the usual browsing appearance.

The editor does not automatically scroll through the entire page to preload content when you start editing. Deferred-content loading runs before export according to your settings. Content that requires a click still needs to be expanded manually.

Export a selected element as PDF

  1. Select the article, table, or component in Visual. Use the DOM tree to choose its outer container if necessary.
  2. Apply the style changes you want and confirm that they appear on the webpage.
  3. Open the arrow beside the export button and select Export selected node.

The main export button exports the full page. Both menu options perform a one-off action; they do not become a saved default. Selected-node export is unavailable until a valid node is selected.

This prepares the selected region as standalone page content and sends it through the PDF pipeline. It does not simply turn the selection rectangle into an image. Applied edits are included. Percentage widths, positioning, and responsive layout may change when the region is laid out as a standalone page, so check the preview rather than expecting an exact crop at the original screen coordinates.

Find and save settings

The toolbar popup's settings button opens a separate settings page. The side panel also has a Settings tab on its home screen. Quick, Custom, and Visual keep separate configurations and save changes automatically. Check that saving succeeded before starting another task; there is no separate Save button.

Extension preferences are separate from PDF layout options:

PreferenceCurrent defaultPurpose
Visual panel locationBrowser side panelCan be changed to an in-page panel.
Interface languageAutomatic (browser language)Choose among 11 languages in Extension preferences. The choice is saved automatically; English is used when no supported language matches. The browser controls the installed extension's name and description.
Selection outlineBlue #2563eb, 2 pxChange the color and thickness when the outline blends into the page.
Webpage context menuEnabledAdds the three conversion entries to ordinary webpages; disabling it removes them.
Maximum screenshot dimension16000 pxAccepts 1000–16000 px. Long pages are tiled without first creating a single oversized image.

Tile dimensions do not determine PDF page count. Quick still aims for one continuous page, scaling the whole result proportionally when necessary. Custom's preview tiles do not replace its paper-based pagination.

The context menu's Quick and Custom entries can currently open the website to display a local conversion result, unlike the toolbar's side-panel flow. A result shown on the website does not mean that a cloud browser reopened the source page. Check the selected conversion service to distinguish the two.

Why Chrome shows a debugger banner

Chrome debugger banner displayed while the extension converts a webpage

The browser displays this notice when the extension uses its debugging interface for viewport, rendering, screenshot, and PDF operations. This screenshot comes from a development build; the extension name may differ in the released version.

Leave the banner open during conversion. Its Cancel button disconnects the debugging session immediately, which can interrupt capture before normal restoration finishes. Use the conversion panel's cancellation control when you need to stop. Read how webpage-to-PDF conversion uses the debugger for the technical explanation.

Restore the page after an error

End the task, then reopen the toolbar popup. The extension checks for possible conversion viewport or rendering overrides left behind. If Restore page display appears, select it. This check targets browser display settings that may survive a page refresh; it is not a universal undo for every webpage interaction.

Forms, collapsed sections, and other script-driven state may not be fully recoverable. Save unsubmitted work before refreshing. If scrolling or display problems remain, note the failed stage and error text and follow the troubleshooting guide. Repeatedly dismissing the debugger banner is not a recovery method.