TL;DR
You rarely want the whole page. You want the pricing table, the one chart, the recipe card, the comparison grid — without the nav, the ads, the cookie banner, and the 400 comments underneath it. Capture Element in Convert: Web to PDF lets you click a single element or region on the page and export only that, as a real PDF with selectable text and working links. It runs 100% locally in your browser, works on pages behind a login using your existing session, and nothing gets uploaded anywhere. Unlike a screenshot tool, you're not flattening the content into an image — the numbers in that table stay copyable and the links stay clickable.
The problem with "save page as PDF" when you only want one thing
Most of the time when people reach for a PDF, they're not archiving a page. They're extracting one useful part of it:
- A single pricing table to drop into a proposal
- One dashboard chart for a weekly status doc
- A recipe card without the food blogger's 1,200-word life story above it
- A comparison table from a review site
- The rendered output of a code snippet (a chart, a result panel, a diagram)
Save the full page and you get all of that buried under a header, a sticky sign-up bar, an ad rail, a "related articles" carousel, and a comment thread. Then you're cropping in a PDF editor, or screenshotting and pasting, and the clean thing you wanted is now a fuzzy rectangle.
Capture Element skips all of that. You select the one element, and the export contains that element and nothing else.
What Capture Element actually does
You activate Capture Element, then hover over the page. The extension highlights whatever element you're pointing at — a table, a card, a chart container, a section. Click it, and that becomes your selection. Then you preview and export.
Two things make this different from cropping or screenshotting:
- It selects a real DOM element, not a pixel region you drew by hand. So the boundaries snap to the actual table or card. You're not eyeballing a rectangle and clipping half a row.
- The output is a real PDF, printed through Chrome's own print engine. Text stays selectable. Links stay clickable. If that pricing table has a "Contact sales" link in a cell, it still works in the PDF.
For the definitional walkthrough — exactly which elements you can grab and how the picker behaves — see the Capture Element entry in the FAQ. This post is about when and why you'd use it.
Honesty note: you select what's rendered, not what's hidden
Capture Element grabs what's actually on the page at the moment you select it. There's no OCR and no magic — if a chart is drawn as an image, you capture that image; if a table is HTML, you capture the live text. If part of the element is lazy-loaded and hasn't appeared yet (a long table that loads rows as you scroll, a chart that renders on view), scroll it into view first so it's fully rendered before you capture. The extension pre-scrolls to help lazy images load, but you can't capture something that never loaded.
Capture Element vs. full-page capture vs. screenshot tools
| Approach | What you get | Text selectable? | Links work? | Clutter included? |
|---|---|---|---|---|
| Capture Element (Convert: Web to PDF) | Just the one element you clicked | Yes | Yes | No — only your selection |
| Full-page PDF | The entire page, top to bottom | Yes | Yes | Yes — everything |
| GoFullPage / screenshot tools | A flattened image of the page (or a region) | No — it's an image | No | Depends; usually yes |
| Chrome's built-in Ctrl+P | The whole page with headers/footers | Yes | Yes | Yes |
| Manual crop in a PDF editor | Whatever you clipped by hand | Sometimes | Sometimes | Whatever you didn't crop |
The row that matters most: screenshot tools flatten everything to an image. GoFullPage and similar utilities are great at what they do — capturing a tall page as one long PNG — but the result is pixels. You can't copy the price out of the table. You can't click the link. You can't search the text. For a section you actually want to use — paste into a doc, quote a number, follow a reference — a real PDF with live content beats an image every time.
Real workflows
Pull one pricing table into a proposal
You're comparing three vendors and want to drop each one's pricing tier into a client deck as a clean reference. Full-page saves would give you three cluttered documents. Instead: open each vendor's pricing page, activate Capture Element, click the pricing table, preview, export. Three tidy PDFs, each just the table, each with the "per seat" links still clickable. If the table is wide and gets clipped on the right, switch to landscape or a wider paper size — that's covered in Fit a wide table or dashboard on one PDF page.
Grab one chart from a live dashboard
You keep an internal analytics dashboard open, and every Friday you paste one chart into a status doc. Screenshotting means a blurry image that ages badly. Capture Element grabs just that chart container as a PDF. Because the extension runs locally using your existing logged-in session, it works on the dashboard behind your company login — nothing is uploaded, and you're not sharing credentials with a server. More on that in Save webpages behind logins as PDF.
Save a recipe card, not the food blog
Recipe pages are the canonical example of "one useful element, 90% padding." The card with ingredients and steps is a discrete element. Point, click, export — you get the card, not the personal essay, not the mid-scroll video ad, not the newsletter gate. If you'd rather clean the whole page into a reader view instead, that's Article Mode's job — see Save an article as a clean PDF.
Keep a code snippet's rendered output
Documentation and tutorial pages often render the result of a code example — a live chart, a formatted table, a component preview. You want to keep that output. Capture Element grabs the rendered panel. One caveat: if the page is heavy on <pre> code blocks and you want to preserve the raw formatted code, use the default mode rather than Article Mode — Mozilla's Readability (which powers Article Mode) can drop <pre> blocks. For capturing a rendered output element specifically, Capture Element in default handling keeps it intact.
Archive one comparison table from a review site
Review and "best of" sites bury a genuinely useful comparison table under affiliate boxes, sticky newsletter bars, and a wall of body copy. You want the table — the one that lines up the five options across price, features, and verdict — so you can reference it later without re-loading a 3MB ad-heavy page. Capture Element grabs just the table. The verdict links in each row still work, and you can copy a spec straight out of a cell. Six months later, when the live page has changed its picks, your captured PDF still shows what the comparison said the day you saved it.
Save a support-doc step, not the whole manual
Product documentation pages are long, and often you only need one procedure — the numbered steps for a single task, plus the callout box warning you about the gotcha. Capture that section as its own PDF and you've got a focused reference you can hand to a teammate or keep in a runbook folder, instead of a 40-screen document where the relevant part is section 7.3. Because it's a real PDF, any in-step links to related settings stay live.
Speed matters: this is a few clicks, not a project
Part of earning the install is respecting your time. The whole Capture Element flow is: activate it, hover to the element you want, click, glance at the preview, export. There's no account, no upload wait, no "processing on our servers" spinner, no watermark to pay to remove. You can bind the extension to its keyboard shortcut (Ctrl+Shift+P) and make the whole thing muscle memory. For a task you might do a dozen times a week — pulling one table, one chart, one card into your own work — shaving it down to a few seconds is the entire point.
When to use full-page instead
Capture Element is the right tool when you want part of a page. Reach for full-page capture when:
- You need the whole article or document as a record
- The "element" you want is really the entire content column
- You're archiving for reference and clutter doesn't bother you
For very long scrolling pages saved end to end, see Save a full scrolling page as PDF. And if it's one section you want but it lives across several elements, you can also use Remove Elements to delete the surrounding clutter first, then export what's left — covered in Hide sensitive details before saving a webpage as PDF.
Why "real PDF" beats "image of the thing"
It's worth being blunt about this because it's the whole point:
- Selectable text means you can copy a figure out of the captured table, or Cmd+F to find a term inside it.
- Clickable links mean references, source links, and CTAs survive.
- Sharp at any zoom — vector text and layout scale cleanly; a screenshot pixelates.
- Smaller, cleaner files for text-heavy content.
A screenshot answers "what did this look like." A real PDF answers "what did this say, and can I use it." For a section you're pulling into your own work, you almost always want the second one.
Frequently asked questions
How is Capture Element different from just taking a screenshot?
A screenshot flattens the region into an image — the text isn't selectable and links don't work. Capture Element exports the selected element as a real PDF through Chrome's print engine, so text stays copyable and links stay clickable. You're capturing the content, not a picture of it.
Can I capture something on a page that requires me to log in?
Yes. The extension runs locally in your browser using your existing session, so it can capture elements on pages behind a login just like you see them. Nothing is uploaded to a server — see Save webpages behind logins as PDF for the full picture.
Does Capture Element use OCR to read the element?
No. There's no OCR anywhere in the tool. It captures the element exactly as it's rendered in the page — live HTML text stays as text, and an image stays as an image.
What if part of the element hasn't loaded yet?
Scroll it fully into view first so it renders completely, then capture. The extension pre-scrolls to help lazy images load, but it can only capture what's actually on the page — anything that never loaded won't appear.
The captured element gets cut off on the right — how do I fix that?
That's a paper-width issue, not a capture issue. Switch to landscape or a wider paper size (Ledger, A3, Tabloid) and adjust scale in the customization options. Full walkthrough in Fit a wide table or dashboard on one PDF page.
Which browsers does this work in?
Any Chromium-based browser — Chrome, Edge, Brave, Arc, Opera, and Vivaldi. It does not work in Firefox or Safari, which don't support the underlying Chrome extension APIs.
Can I capture more than one element at once?
Capture Element targets one element or region per export. If you want several scattered pieces, capture them separately, or use Remove Elements to strip everything except the parts you want and export the remainder as one PDF.
Bottom line
Most PDFs start with someone wanting one clean thing off a messy page. Capture Element in Convert: Web to PDF gives you exactly that — click the table, the chart, the card, the output panel, and export just that as a real PDF with live text and working links. It's local, it works behind logins, nothing gets uploaded, and it's free. Point at the thing you actually wanted. Skip everything else.