skwish

private

browser-based

Compress bug-report screenshots to fit GitHub's 10MB attachment cap

GitHub's attachment limits are different from its repository limits, and that catches people mid-bug-report. In issue comments, pull request comments, and discussion comments the maximum is 10MB for images and gifs, 25MB for everything else. A full-screen capture from a 5K display as an uncompressed PNG can clear 12 MB before any annotation, so drag-and-drop silently fails on exactly the screenshot that shows the bug best. The practical ceiling is far lower than 10MB anyway, because a reviewer scrolling a pull request does not want to download a 9 MB image to see a misaligned button — a lossless-looking PNG at the actual pane width is usually 200-500 KB. Another constraint worth knowing is format: GitHub's supported image types in all contexts are PNG, GIF, JPEG and SVG, which means HEIC straight off a Mac screenshot-and-annotate flow is not a safe bet, and converting to PNG or JPEG solves both the format and the weight problem in one step. Skwish handles the conversion and the compression in the browser, shows a before/after size per file, and lets you drop several screenshots at once and take them back as a ZIP. Nothing is uploaded, so screenshots of private code stay private.

Search match

This page is tuned for compress image for github issue so visitors land in the right workflow immediately.

Fast output

See original size, compressed size, and percentage saved before you move on.

Batch ready

Compress multiple files and pull the results down as a ZIP.

Get to the compressor fast

Exact-intent SEO page first. Clear next step. Pretty later.

People usually search for a specific task, not a brand story. So this page keeps the promise simple: compress images without sending them to a third-party server.

Built for people searching “compress image for github issue”, not a generic landing page.

No uploads, no accounts, no waiting on a server.

See the savings before you download anything.

Batch export stays available when the job is bigger.

Best for this search

Get a 12 MB full-screen retina capture under GitHub's 10MB image attachment limit without losing the detail that shows the bug.

Convert HEIC or oversized screenshots to PNG or JPEG, the formats GitHub actually accepts in issue and PR comments.

Compress a set of before/after reproductions for a pull request so reviewers are not downloading megabytes per comment.

Compress images now

Opens the upload box on the free browser compressor.

Drop images in the browser

Keep the whole workflow local. Nothing leaves your device unless you download it.

Set the output you need

Adjust compression until the file size and quality fit the job instead of guessing.

Download a clean result

Save one file or a ZIP bundle with skwish-prefixed names so the output is easy to find.

Attachment caps are not repository caps

Use these before you upload or share the page.

Issue and PR attachments: 10MB per image or gif, 25MB for other file types. Repository files are a different scale entirely — 25 MiB via browser, 100 MiB via CLI.

Supported image types in comments are PNG, GIF, JPEG and SVG. HEIC is not on that list, so a straight screenshot upload from macOS can fail on format, not size.

Aim far below 10MB. A screenshot sized to the review pane is 200-500 KB and reads the same as a 9 MB original.

Ready to compress images?

Open the free browser upload box, keep files local, and download the optimized result.

Compress images now

Related tools

Other compression pages built for specific size limits and formats.