Save a Webpage as PDF on iPhone and Android (2026)

TL;DR

Both iPhone and Android can save a webpage as a PDF without installing anything — it's built into the Share sheet and the print dialog. On iPhone: tap Share → Print → pinch open on the print preview thumbnail → tap the share icon in Markup → Save to Files. On Android Chrome: tap the 3-dot menu → Share → Print → choose "Save as PDF" from the printer dropdown → tap the save icon. Both methods are "print to PDF" in disguise, so you get headers, footers, ads, cookie banners, and whatever the page's print stylesheet decides to keep — with no way to fix any of it on the phone.

If you know you'll be at a computer later, even briefly, the better move is to bookmark the page or email yourself the link, then re-save it there. Convert: Web to PDF is a free Chrome/Edge/Brave/Arc extension that strips clutter, extracts clean article text, and produces a real selectable-text PDF with clickable links — something no phone's built-in print-to-PDF can do. It's a desktop-only tool (Chrome extensions don't run on mobile browsers at all), so think of it as "step two" after the quick phone save, not a replacement for it.

Why there's no "mobile app" answer here

Worth saying plainly, because a lot of search results dance around it: Chrome extensions cannot run on iOS or Android. Mobile browsers — Safari on iPhone, Chrome on Android, any mobile browser app — don't have an extension system the way desktop browsers do. If a site or app claims a Chrome extension "works on your phone," that's not accurate. So the honest starting point for mobile is the native save-as-PDF feature each phone already has built in. It's genuinely useful for quick, one-off saves. It just isn't as capable as what a real desktop browser can do with the same page.

That's the shape of this whole guide: native mobile steps first (because they work and people need them), an honest look at what's missing, and then what to do about it if quality matters more than speed.

How to save a webpage as PDF on iPhone (iOS Safari)

iPhone doesn't have an explicit "Save as PDF" button sitting in the Share sheet — it's tucked inside the Print flow, and the trick is a pinch gesture almost nobody discovers on their own.

1. Open the page in Safari.
2. Tap the Share icon (the square with the arrow pointing up), usually at the bottom of the screen or top-right on iPad.
3. Scroll down the share sheet and tap Print.
4. On the print preview screen, you'll see a small thumbnail of the page. Pinch outward (spread two fingers) on that thumbnail — this is the part people miss. It expands into a full Markup view of the rendered PDF.
5. In Markup view, tap the share icon again (top-right).
6. Choose Save to Files (recommended — this keeps it as an actual .pdf file you can find later, unlike Save to Photos, which is really meant for images).
7. Pick a folder in iCloud Drive or On My iPhone and save.

Alternative shortcut on some iOS versions: in the Print dialog, tap Options (or long-press the share icon on newer iOS builds) and look for an Export PDF action that skips the Markup detour entirely. Availability varies by iOS version and app, so if you don't see it, the pinch-to-expand method above always works.

Either way, what you get is Safari's print engine's interpretation of the page — not the live, interactive page you were just scrolling through.

How to save a webpage as PDF on Android (Chrome)

Android's path is more direct because "Save as PDF" is a literal option in the printer list.

1. Open the page in Chrome for Android.
2. Tap the 3-dot menu (top-right).
3. Tap Share, then Print. (On some Chrome versions, Print is its own menu item — no need to go through Share first.)
4. On the print screen, tap the printer dropdown at the top (it may default to a nearby physical printer or say "Save as PDF" already).
5. Select Save as PDF from the list.
6. Tap the download/save icon to generate the file.
7. Choose a location (usually your Downloads folder) and confirm.

Same underlying idea as iPhone: Chrome hands the page to Android's print pipeline, which renders it as a PDF using the page's print stylesheet — not necessarily the page you were actually looking at.

What's actually lost doing it natively

Both native methods are running the page through a print engine, not a purpose-built PDF export. That distinction is the source of every limitation below. Print stylesheets are designed to save ink and paper, not to make a clean digital archive — they were never built with "I want to keep this forever" in mind.

Specifically, on both iPhone and Android, you're stuck with whatever the page's print CSS decides to do:

• Headers and footers you can't remove. Some sites inject their own URL/date footer via print stylesheets; the OS may add its own too. No way to strip either on-device.
• Layout breakage. Multi-column layouts, sticky headers, embedded widgets, and JS-rendered content can render oddly or get cut off, because you're at the mercy of the site's print CSS (if it has one at all).
• Ads and clutter often survive. Print stylesheets are supposed to hide navigation and ads, but plenty of sites don't bother maintaining print CSS anymore, so you get the full page — nav bar, cookie banner, related-articles rail and all — baked into your "clean" PDF.
• No selective removal. If a page is 80% content and 20% junk, you're taking all of it. There's no click-to-delete step on a phone print dialog.
• Minimal margin/paper control. You typically get portrait/landscape and maybe a couple of paper sizes — nothing like custom margins or scale.
• No article extraction. There's no reader-mode-style pass that pulls just the article text and drops the rest.

None of this is a knock on the phones — Apple and Google built genuinely useful, zero-install features here. It's just that "print to PDF" was never designed to be a content-cleanup tool, on any platform.

Native print-to-PDF vs. Convert: Web to PDF (desktop)

The "login-protected pages" row matters more than it looks: neither approach can magically see behind a login you haven't already passed. The advantage both share is that they run in a browser where you're already signed in — a server-side "URL to PDF" tool couldn't do that at all.

When mobile-native is actually the right call

None of the above means you should always wait for a computer. The built-in phone method is genuinely the correct tool in a few situations:

• You need it saved right now and don't know when you'll next be at a desktop — a rough PDF beats no PDF.
• It's a quick reference save — a receipt confirmation, a boarding pass backup, a recipe you're about to cook from — where appearance doesn't matter, only that the content exists somewhere offline.
• The page is already print-friendly — plain-text articles, simple invoices, and government forms often survive print-to-PDF just fine because they don't have much clutter to begin with.
• You just need proof of what a page said at a specific moment, not a polished document.

For all of these, pinch-to-expand on iPhone or "Save as PDF" on Android does the job in under 30 seconds. Don't overthink a quick save.

The better move when a computer is coming

If you know you'll be near a laptop or desktop later — even just once, even hours from now — it's worth holding off on the phone save (or keeping the rough version as a placeholder) and redoing it properly on desktop instead. The workflow:

1. On your phone, bookmark the page, or email/message yourself the link. Either takes five seconds and costs nothing.
2. Later, on a Chromium desktop browser (Chrome, Edge, Brave, or Arc), open the link.
3. Click Convert: Web to PDF in the toolbar.
4. If it's an article, try Article Mode first — it strips navigation, ads, and sidebars automatically using a reader-view extraction. (Skip Article Mode for anything code-heavy — it can drop <pre> code blocks, so use the default full-page mode for documentation or Stack Overflow-style pages.)
5. If Article Mode isn't a fit, use Remove Elements to click away ads, cookie banners, and clutter by hand — there's an undo if you remove something you wanted.
6. If the page uses lazy-loaded images, run Load All Images first so nothing renders as a blank gap.
7. For long feeds or listings, scroll to load everything you want captured before converting — infinite-scroll pages only capture what's currently rendered, same limitation as the phone method, so this step matters either way.
8. Adjust margins, scale, or paper size (up to A3/Ledger) if the default doesn't fit your needs, then download.

The output is a real PDF with selectable, searchable text and working hyperlinks — generated by Chrome's own print engine, not a phone's print stylesheet interpretation. And like the native methods, it runs entirely in your browser: nothing is uploaded anywhere, and it works on pages behind a login just as well as public ones.

This isn't a hard sell to install something on your phone — you can't, because Chrome extensions don't run on mobile browsers at all. It's simply "do the rough save now, do the clean save later if it's worth the extra two minutes."

Frequently asked questions

Can I install Convert: Web to PDF on my iPhone or Android phone?

No. Chrome extensions only run on Chromium desktop browsers — Chrome, Edge, Brave, and Arc on a computer. iOS and Android browser apps (including mobile Chrome) don't support the extension APIs that Chrome extensions rely on, so there's no version of this — or any Chrome extension — that installs on a phone.

Why does my iPhone PDF have weird headers or cut-off content?

That's the print stylesheet at work. Safari renders the page through the same engine used for physical printing, and many sites either don't maintain print CSS anymore or inject their own footer with the URL and date. There's no on-device way to edit that output — you're stuck with whatever the page's print rules produce.

Is "Save as PDF" on Android the same as printing?

Yes, functionally. Android's "Save as PDF" option in the printer dropdown uses the exact same rendering pipeline as printing to a physical printer — it just writes the output to a file instead of sending it to a printer. Any print-related quirk (missing content, broken layout, injected headers) shows up in both.

Can I save a webpage as PDF on my phone without opening the Share menu?

Not really — on both platforms, saving to PDF is a variant of the print flow, and print is reached through the Share sheet on iPhone (or the 3-dot menu on Android Chrome). There's no separate one-tap "save as PDF" button outside of that path on either OS as of 2026.

Will the mobile PDF have clickable links and selectable text?

Usually yes for text and links, since both platforms render actual PDF pages rather than flat images. What you don't get is control over what's included — ads, navigation, and cookie banners often come along for the ride if the site's print stylesheet doesn't hide them.

What if the page uses infinite scroll, like a social feed?

Scroll to load everything you want to capture before you print, on either phone or desktop. Neither the native print-to-PDF flow nor Convert: Web to PDF can capture content that hasn't loaded yet — both only work with what's currently rendered on the page.

Does emailing myself a link work as well as a bookmark?

Yes, either works. Pick whichever is faster for you — a bookmark stays in your browser, an emailed link is easy to find later even from a different device. The point is just getting the URL somewhere you'll see it when you're back at a computer.

Bottom line

iPhone and Android both have a real, free way to save a webpage as PDF, and it's worth knowing the exact steps: pinch-to-expand in Safari's print preview, or "Save as PDF" in Android Chrome's printer list. Use it for quick saves where speed matters more than polish.

When you know a computer is in your near future, hold onto the link instead and redo the conversion there. Convert: Web to PDF — free for Chrome, Edge, Brave, and Arc — turns the same page into a clean, selectable-text PDF with article extraction, one-click clutter removal, and full layout control, all processed locally with nothing uploaded.