What it does

Go Full Screenshot captures the whole page — not the visible window, the entire document, including everything below the fold — from a single click on the toolbar icon. The capture opens straight into an editor, where you can annotate it, hide the parts that should not be shared, wrap it in a browser frame, and export it as a PNG, a WebP or a PDF.

That is the entire loop: click, mark up, export. There is no upload step, no share link to manage afterwards, and no account standing between you and the image.

One click, the whole page

Most screenshot tools open with a question: full page, visible area, or a selection? Go Full Screenshot answers it by default. Press the button and it scrolls the document, captures it in slices, and stitches those slices into one continuous image at the page’s real width.

Long pages are treated the same as short ones. A documentation page, a pricing table, a long thread, a dashboard that runs three screens deep — each comes back as a single image instead of something you have to reassemble by hand in another application. A page that scrolls for thirty seconds still takes one click.

Sticky headers are the classic failure of stitched screenshots: a fixed navigation bar repeats down the finished image, once per slice, and the result is unusable. Go Full Screenshot accounts for fixed and sticky elements while it scrolls, so that navigation bar appears once, at the top, where a reader expects it.

The editor

A screenshot is rarely finished at the moment it is taken. Something needs pointing at, something else needs hiding, and the whole thing usually needs to look deliberate rather than accidental. That is what the editor is for, and it opens automatically with the capture already loaded.

Arrows, shapes and text

Arrows are the workhorse. Drag one from the margin to the thing you are talking about, and the person reading your bug report stops hunting for the button you meant. Shapes — rectangles, ellipses and lines — do the same job when you need to enclose a region rather than point at it. Stroke weight, colour and corner radius are adjustable, so a highlight can be loud on a light interface and still readable on a dark one.

Text boxes add the sentence the arrow cannot say: a step number, an expected value, a short note to a colleague. Size, colour and a background plate are available, because white text on a white dashboard is the fastest way to make an annotation invisible.

Blur and focus

Blur is the tool that matters most, and the one people reach for last. Drag it across an email address, an API key, a customer name, an account balance, a face in a testimonial, and it is gone. The blur is applied to the pixels themselves on export, not layered over them as a mask that someone could remove from the file afterwards.

Focus takes the opposite approach. Instead of hiding what is sensitive, it dims everything except the region you mark, which is the quickest way to point a reader at one card in a busy dashboard without cropping away the context that makes the card make sense.

Between the two, most of the “can I share this screenshot?” hesitation disappears. You are not choosing between a useful image and a safe one.

Frames, browser mockups and backgrounds

A raw screenshot dropped into a landing page or a slide deck looks like evidence. The same screenshot inside a browser mockup — window chrome, a URL bar, rounded corners, a soft shadow — looks like a product.

Go Full Screenshot includes browser mockups for exactly that, along with frames, padding and background options for presentations, changelogs, blog posts and app store assets. It is the difference between a screenshot you attach to a ticket and one you put on a page where people are deciding whether to trust you.

Stickers and emoji

Stickers and emoji sound frivolous until you write support replies or tutorials for a living. A green check beside the correct setting and a red cross beside the wrong one carry a step-by-step instruction faster than a paragraph, and in a language-neutral way. They are also the cheapest way to make an internal document feel like it was written by a person.

Copy, or export as PNG, WebP or PDF

The fastest export is not a file at all. Copy the image and paste it straight into Slack, Jira, Linear, Notion, Google Docs or Figma — no download folder, no filename, no cleanup later.

When you do need a file, there are three formats, and the choice is not cosmetic:

PNG is lossless. Text stays crisp at any zoom and flat interface colours stay exactly as they were. It is the right default for bug reports, documentation and anything containing small type, at the cost of the largest file of the three.

WebP produces a dramatically smaller file at visually equivalent quality — usually a fraction of the equivalent PNG — and it is supported by every current browser. If the screenshot is going into a web page, a knowledge base, a wiki or a ticket where attachment size matters, WebP is almost always the better trade.

PDF turns the capture into a document rather than an image. That is what you want for records that need to survive: receipts, invoices, order confirmations, terms you agreed to on a given day, a page you may need to print or hand to someone who expects a document. PDFs also open the same way on every device, without anyone hunting for an image viewer that can handle a very tall file.

Being able to move between the three from the same capture is the point. One click at the start, and the decision about format comes later, when you know where the image is actually going.

Where it fits

The obvious use is bug reporting: capture the broken page, arrow the broken element, blur the session token, paste it into the ticket. Four steps, no context switch.

Beyond that, the pattern repeats anywhere a page needs to leave the browser. Design review, where the comment only makes sense next to the pixels. Documentation and tutorials, where a numbered sequence of annotated captures beats three paragraphs of prose. Record keeping, where a page that will change — a price, a policy, a booking — is worth a dated PDF. Teaching and support, where a sticker and an arrow remove an entire round trip of “which button?”.

Permissions, and why it needs them

Capturing a page requires real access to it, and it is worth being precise about what that means.

Reading the tab’s contents is what allows the extension to scroll the document, measure it and capture each slice. Saving files is what allows the export button to put a PNG, WebP or PDF in your downloads folder. Browser storage keeps your editor preferences — the colours, the last export format — between sessions.

What none of that requires is a server. Capture, editing and export all happen locally, in the browser, which is why there is no account and no upload step. The image is on your machine, and it stays there until you copy or save it deliberately.

Things to know

No screenshot tool captures everything, and the limits are worth knowing before you hit a deadline with one.

Pages that draw themselves on a canvas or in WebGL — some map tools, charting libraries, in-browser games and video players — can come back blank or black, because the browser deliberately restricts reading those pixels.

Aggressively lazy-loaded images sometimes need a moment. The capture scrolls the page, which triggers most lazy loading, but a page that only loads images after an idle delay may need one manual scroll to the bottom first.

Very long pages meet a hard browser limit on image dimensions. Beyond a certain height the export has to be scaled down to fit, which is the trade every full-page capture tool makes at that size — PDF is usually the better export there.

Browser-internal pages — settings, the extensions page, the web store — cannot be captured by any extension, because no extension is permitted to run on them.

Go Full Screenshot is built and maintained by us, and this page is kept in step with what the current version actually does. If something here does not match what you see after installing it, that is a bug in the page and we want to hear about it.