How to compress a screenshot before sending it in Slack or Teams

A modern laptop or external monitor captures at very high resolution. A 14-inch MacBook Pro screen is 3024 by 1964 pixels — about 6 megapixels per full-screen screenshot. A 27-inch 4K monitor is 3840 by 2160, also 8 megapixels. Even a single application window on these displays is often 2,000 pixels wide or more.

Operating systems save screenshots in PNG by default. PNG is a great choice for screenshots in principle because it preserves text and UI edges sharply with no compression artifacts. But PNG is also a large format — a single full-screen screenshot on a 4K display is routinely 3 to 6 MB, and a screenshot of a code editor or text-heavy document can be even larger because the pattern of letters generates many color transitions that PNG compresses less efficiently than uniform colors.

Most of the time, the recipient does not need that resolution. A screenshot shared in Slack to ask is this what you meant, or to flag a bug, is going to be viewed inline at 600 to 800 pixels, then maybe clicked to view at 1,200 pixels. The remaining 1,000 or more pixels of source data carries no information the viewer can actually use, but it costs everyone bandwidth and storage.

• A 4K screenshot is 8 megapixels and often 3 to 6 MB on disk.
• PNG preserves screenshot quality but produces large files.
• Inline viewers display screenshots at 600 to 800 pixels regardless of source resolution.
• Most of the file size in a typical screenshot is data the recipient never sees.

Both Slack and Microsoft Teams accept large files but handle them differently in ways that matter for everyday use.

Slack uploads images up to 1 GB per file for paid plans (significantly smaller on free plans, and aggregate storage limits apply). Slack does generate thumbnails for inline preview, but the full file is what gets stored and counts against your workspace storage limit. Free Slack workspaces have a 10 GB storage cap — large screenshot files chew through this faster than most teams expect. Slack also re-compresses some images during upload to improve preview performance, but only modestly.

Microsoft Teams has higher limits for paid plans (up to 250 GB per file on most enterprise SKUs) and integrates with OneDrive or SharePoint for actual storage, so the storage cap depends on the underlying Microsoft 365 plan rather than Teams itself. Teams also generates inline previews but stores the full file.

For most teams, the practical limit is not the platform cap — it is search and scroll performance. Channels with hundreds of multi-megabyte screenshots become slow to load and slow to search. Smaller screenshots load faster, search faster, and keep the channel feed snappy.

• Slack free workspaces have a 10 GB storage cap; large screenshots burn through it quickly.
• Teams stores files in OneDrive or SharePoint; the limit depends on the M365 plan.
• Both platforms generate inline previews but store the full original file.
• The real-world constraint is channel performance, not the platform file-size cap.

The cleanest workflow for an everyday user is to capture the screenshot, compress it, and paste or upload to the chat — adding about three seconds to the share process while keeping file size sensible.

For screenshots of UI elements, documents, and code where text needs to stay crisp, run the file through the Image Compressor using lossless or near-lossless compression. This produces 60 to 80 percent smaller files than the original PNG with no visible quality loss. A 4 MB screenshot drops to 800 KB to 1.5 MB, still PNG, still sharp.

For screenshots of mostly photographic content — a webpage with hero images, a video frame, an app screen with lots of color photos — converting to JPG produces much larger savings. The File Converter handles PNG to JPG conversion in one step. JPG quality 85 to 90 keeps photographic content clean and produces files 70 to 90 percent smaller than the original PNG. Avoid JPG for screenshots with significant text — the compression artifacts show up around letters and harm readability.

If the screenshot has both UI text and photographic content, default to lossless PNG compression. The text-preservation matters more than the marginal extra size savings JPG would provide.

• Lossless PNG compression cuts screenshot file size by 60 to 80 percent with no quality loss.
• JPG quality 85 to 90 is the right choice for screenshots dominated by photos.
• Avoid JPG when screenshots contain significant text or UI elements.
• For mixed content, default to PNG to preserve text crispness.

The single biggest file-size win for screenshots is often not compression — it is cropping. A full-screen capture sent to ask about a 200-pixel button is mostly wasted pixels. Cropping to just the relevant area before sending cuts the file by 80 to 95 percent and also helps the recipient see what you are pointing at without having to scan the whole image.

On macOS, the built-in screenshot tool (Cmd Shift 4) captures a selected area directly, which is usually a better starting point than the full-screen capture (Cmd Shift 3). On Windows, the Snip and Sketch tool (Win Shift S) does the same thing. Both produce smaller, more focused screenshots without requiring a separate crop step.

When annotation matters — pointing to a specific bug, highlighting an option — use a dedicated screenshot tool that combines capture, annotation, and export. Greenshot, ShareX, and CleanShot X on Mac all handle this. Markup tools also typically save in compressed PNG or in JPG, depending on settings, which is often smaller than the raw OS capture.

• Cropping before sending cuts file size by 80 to 95 percent.
• Use the macOS area-capture shortcut (Cmd Shift 4) instead of full-screen.
• On Windows, Snip and Sketch (Win Shift S) captures only what you need.
• Dedicated screenshot tools (CleanShot X, ShareX, Greenshot) combine capture, crop, and annotation.

Some workflows produce many screenshots at once — bug reports with multiple steps, design review sessions, support cases involving several error states. For these, batch compression is much faster than handling each file individually.

The general flow is to capture all the screenshots you need to share in one session, drop the resulting files into a single folder, then run them as a batch through the Image Compressor or File Converter. Both tools accept multiple files in one upload, apply the same settings across the batch, and produce a single download (often a ZIP of all outputs). For a folder of 20 screenshots, this takes about 30 seconds total versus three or four minutes one at a time.

For ongoing batch needs — a support team that produces dozens of screenshots a day — consider a screenshot tool that compresses on capture. CleanShot X and ShareX both have settings to save captures as compressed PNG or as JPG by default, so the compression step never has to happen as a separate task. This is the highest-leverage configuration change for teams whose screenshot volume is high.

• Batch compression handles a folder of screenshots in seconds, not minutes.
• Both the Image Compressor and File Converter accept multiple files in one upload.
• For high-volume use, configure your screenshot tool to compress on capture.
• CleanShot X and ShareX both support compress-on-capture out of the box.

A few habits silently fill channels with oversized screenshots.

Sharing screenshots of entire web pages when only a small section was relevant is the most common one. A full-page screenshot of a long article can easily be 5 to 10 MB. Crop to the paragraph or element you are referencing.

Sending the same screenshot multiple times across different threads, instead of linking back to the original message, is another common pattern. Slack and Teams both store each upload as a separate file. A frequently-referenced screenshot gets uploaded ten times by ten people instead of one time with permalinks shared.

Using screen recording when a screenshot would have worked — pressing the wrong key combination and recording a video of a static screen — produces a file 50 to 500 times larger than the equivalent screenshot for no extra communication value. Many keyboard-shortcut mistakes are easy to make on macOS especially; check the file type before uploading.

Pasting screenshots from the clipboard into a chat message often results in a different (and sometimes larger) version than the file saved to disk, because the clipboard image can include uncompressed bitmap data. Saving to file first and then attaching gives more predictable file sizes.

• Crop full-page screenshots to the relevant section before sending.
• Link back to existing screenshots instead of re-uploading them across threads.
• Watch for accidental screen recordings; they are 50 to 500 times larger than screenshots.
• Save to file then attach for more predictable file sizes than pasting from clipboard.