Chrome Full-Page Screenshot Too Large? 5 Fixes That Work (2026)

You saved a full-page Chrome screenshot, went to attach it to the ticket, and the file will not upload. The re-capture produced the same oversized PNG. The built-in output is one lossless image sized to the full scroll height times page width, with no compression control. Five fixes below shrink it.

Fix 1: Capture a region instead of the full page

One way to shrink a full-page screenshot is to not take one. If the ticket needs the pricing table and nothing else, a region capture produces a file a fraction of the size of the full scroll-height PNG. SuperchargeCapture’s region mode (suggested shortcut Alt+Shift+R) lets you drag a rectangle around exactly the pixels you need.

The suggested keys are rebindable. If another extension has claimed Alt+Shift+R, Chrome silently drops the binding, so check the extension shortcut page if the key does nothing.

Fix 2: Export as JPG or WebP instead of PNG

If you need the full page but the PNG is still too heavy, switch the export format. SuperchargeCapture writes captures to disk in PNG, JPG, or WebP. JPG and WebP are lossy formats: they compress the image by discarding pixel information the eye is unlikely to notice, which makes the file smaller than an equivalent PNG. You lose a little sharpness in dense text or at hard edges, but for a ticket attachment or a paste into a doc, the difference is rare.

Chrome’s built-in DevTools full-size capture saves a PNG. The lossy export option lives in the extension.

Fix 3: Use Chrome’s built-in area capture

Chrome’s DevTools has a command that does what Fix 1 does without an extension. Open DevTools with F12, press Ctrl+Shift+P to open the Command Menu, type screenshot, and select Capture area screenshot. Drag a rectangle around the section you want. The result is a screenshot of that region, not the full document.

Two constraints: DevTools must stay docked to the browser window (area capture will not fire if DevTools is undocked from the window), and the command ships as a preview feature from Chrome 106 onward. If your page is short enough that a regular viewport screenshot covers what you need, skip the full-size path and the file stays small.

Fix 4: Crop or convert the file after saving

If the PNG is already on disk and you just need it under an attachment limit, open it in any image editor (your OS preview app, or a browser-based tool) and either crop it to the section you need or re-export as JPG. Fewer pixels produce a smaller file, and cropping the image to just the part you reference in the ticket is the most reliable cut. This is a manual step.

Fix 5: Shorten the page before you capture

The full-size capture’s pixel count equals the document’s scroll height times its width. If you only need one screen’s worth, SuperchargeCapture’s visible mode (suggested Alt+Shift+S, rebindable) captures just the current viewport. DevTools covers the same ground: F12, Ctrl+Shift+P, run Capture screenshot from the Command Menu.

Which fix to use

For a section of a long page, Fix 1’s region or element mode, or Fix 3’s built-in area capture, gives a small file. Keep the whole page? Use Fix 2’s lossy JPG or WebP export for a smaller file. Already saved the PNG? Fix 4 crops or converts it in an image editor before sending.