How to Save a Webpage as PDF

Browser "Save as PDF" is a mess. Ads, navigation menus, cookie banners — everything gets dumped into your PDF. There's a better way.

The problem with browser saves

You want to save an article for offline reading or archival. You hit Cmd+P, choose "Save as PDF," and get a cluttered document full of sidebar widgets and advertisements. The article you wanted is buried under cookie consent dialogs and newsletter popups.

Browser extensions like PrintFriendly or Mercury Reader strip some clutter, but they break when sites update their layouts, they require accounts, and they add yet another tool to manage. Pocket and Instapaper save articles for later reading, but you don't own the content — it lives on their servers, and if the service shuts down or changes its terms, your archive goes with it.

Your Zo takes a different approach: it reads the webpage with a real browser, extracts just the article content, and converts it to a clean PDF saved to your workspace. You own the file. It's on your server. No service dependency.

Save a page

Your Zo fetches the page using a real browser (handles JavaScript-rendered content, login walls, and dynamic loading), extracts the article text and images using readability algorithms, embeds images directly in the document, converts to PDF using pandoc, and saves it to your workspace so you can download it anytime.

The result is a clean document with just the content — no navigation, no ads, no cookie banners.

Customize the output

Control how the PDF looks:

Your Zo passes formatting options to pandoc, so anything pandoc supports — page size, fonts, column layouts, headers, footers — you can request in plain English.

PDF vs Markdown: when to use which

Your Zo can save pages as either PDF or Markdown. The right format depends on what you're doing with the content afterward.

Save as PDF when:

• You want to read it as-is, offline or on a tablet
• You're sharing it with someone who needs a finished document
• You want to preserve the visual layout (images, formatting, embedded charts)
• You're archiving something for reference and don't plan to edit it

Save as Markdown when:

• You want to search across saved articles later ("Search my saved articles for mentions of transformer architecture")
• You're building a research collection you'll reference, quote, or remix
• You want to feed content into other workflows — summaries, analysis, daily digests
• You plan to edit or annotate the content

Markdown files land in /home/workspace/Articles/ where your Zo can search and reason over them. PDF files are better for archival and sharing. Many people save both: Markdown for working with the content, PDF for a clean reading copy.

Batch saving

Save multiple pages at once when you're doing research or want to archive a reading list:

For larger collections, describe what you want:

Batch saves work well with other tools your Zo has access to. If you have a reading list in Google Drive or links in a Notion page, your Zo can pull the URLs and save them all.

Build a personal archive

66% of links break within a decade. That article you want to reference next year might be a 404 by then. Saving pages to your workspace means you own the content regardless of whether the original site survives.

A few patterns that work well for building a lasting archive:

Organized by topic:

With automated filing:

Scheduled archival:

Over time, you build a searchable personal library on your Zo. Unlike bookmarks that rot, the content is yours.

Getting started

Try saving one article:

Check the result in your workspace. If you like it, try a batch save or set up an archival agent. Your Zo handles the fetching, cleaning, and converting — you just point it at the pages worth keeping.