Screenshot Too Large for Slack, Jira, or Email?
Compress & Convert Images for Any Workplace Platform
Retina screenshots are 5-15 MB PNGs. Figma exports can hit 20 MB. Every workplace platform has different image size limits -- and most are stricter than you think. Compress and convert images offline to keep proprietary work content private.
Workplace Platform Image Size Limits
| Platform | Max Image Size | Notes |
|---|---|---|
| Gmail | 25 MB total | Total attachments; inline images auto-compressed |
| Outlook (Corporate) | 10-25 MB | Admin-set; many orgs default to 10 MB |
| Outlook.com | 20 MB | Personal accounts |
| Slack | 1 GB per file | Generous, but large images slow to load and preview |
| Microsoft Teams | 250 MB per file | Per file in chat |
| Jira | 10 MB default | Admin can increase; rarely do |
| Confluence | 10 MB default | Same as Jira |
| Notion | 5 MB free / unlimited paid | Free tier very restrictive for images |
| Trello | 10 MB free / 250 MB paid | Free tier matches Jira default |
| Asana | 100 MB | Per file attachment |
| Linear | 10 MB | Per file attachment |
| GitHub Issues | 10 MB (most) / 25 MB (certain) | Most image types capped at 10 MB |
| Figma Comments | 4 MB | Most restrictive platform for images |
| Google Docs/Slides | Auto-compressed | Images auto-compressed on insert; source quality matters |
| Zendesk | 50 MB per ticket | Per file in tickets |
| Basecamp | 50 MB per file | Per file upload |
Why Your Screenshots Are So Large
Modern displays capture far more pixels than you need for a Jira ticket or Slack message.
Retina/HiDPI Displays Capture at 2x-3x Resolution
A full-screen Mac screenshot on a Retina display captures at 2x or 3x native resolution, producing a 5-15 MB PNG file. That's 5120x2880 pixels for a 27" display -- far more than anyone needs in a bug report.
Windows 4K Screenshots Are 8-12 MB
Windows Snipping Tool at 4K resolution produces 8-12 MB PNG files. Even a cropped region of a 4K display can easily exceed Jira's 10 MB limit.
iPhone Screenshots Are 3-6 MB PNGs
iPhone screenshots are saved as PNG at full display resolution (2796x1290 on iPhone 15 Pro Max). Taking a few screenshots and emailing them can quickly exceed the 25 MB attachment limit.
PNG Format Preserves Every Pixel
Screenshots default to PNG format, which is lossless -- every pixel is preserved. This is great for accuracy but terrible for file size. Most of that detail is invisible at normal viewing size.
PNG vs JPG vs WebP -- Which to Use at Work
PNG
Screenshots with text, UI mockups, anything with transparency
Largest file size -- a full-screen screenshot can be 5-15 MB
Use when pixel-perfect text rendering matters (code screenshots, UI specs)
JPG
Photos, general images, when file size matters more than pixel-perfect text
Lossy compression -- slight quality loss, but 80-90% smaller than PNG
Use for most workplace sharing -- text stays readable at 90% quality
WebP
Best of both worlds where supported (Slack, web apps, modern browsers)
30-50% smaller than JPG at same quality; not supported everywhere yet
Use for Slack, web-based tools, and anywhere that accepts WebP
Compress PNG screenshots to JPG at 90% quality -- text stays perfectly readable and file size drops from 8 MB to 200 KB. For Slack and web tools, use WebP for even smaller files.
Common Workplace Image Scenarios
Bug Report Screenshot for Jira/Linear
Your Retina screenshot of the bug is 12 MB PNG. Jira and Linear have a 10 MB attachment limit. You need to show the exact error state with readable text.
Convert PNG to JPG at 90% quality. Text stays perfectly readable, file drops from 12 MB to under 500 KB. Alternatively, crop to just the relevant area first.
Compress for Bug ReportsDesign Mockup Feedback in Figma/Slack
Your PNG export from Figma is 5-20 MB. You need to share it in Slack for feedback or attach it to a Figma comment (4 MB limit). Multiple mockups make the problem worse.
Compress to JPG or WebP. Design mockups with flat colors compress extremely well. A 15 MB Figma export becomes 300 KB as a JPG at 90% quality.
Compress Design ExportsProduct Screenshots for Client Email
You need to email 5 product screenshots to a client. Each is 6 MB PNG from your Retina display. Total: 30 MB, exceeding Gmail's 25 MB attachment limit.
Batch compress all screenshots to JPG. Each drops from 6 MB to ~150 KB. Total becomes under 1 MB -- fits easily in any email platform.
Compress for EmailArchitecture Diagram for Confluence
Your exported architecture diagram is an 8 MB PNG. Confluence has a 10 MB limit, but the page loads slowly with large images and you have multiple diagrams.
Convert to JPG or WebP. Diagrams with clean lines and text compress very efficiently. An 8 MB diagram becomes 200-400 KB as JPG.
Compress DiagramsTraining Documentation Screenshots
Your training guide has 20 step-by-step screenshots, each 5-10 MB as PNG. Total image weight: 150 MB. The Confluence page or Google Doc takes forever to load.
Batch compress the entire folder of screenshots. Convert to JPG, resize to reasonable dimensions (1280px width is plenty). Total drops from 150 MB to 4 MB.
Batch Compress ScreenshotsMarketing Assets for Social/Web
You need to share product screenshots in multiple sizes for the website, social media, and sales deck. The original PNG is 15 MB and needs to be resized for each platform.
Resize and compress in one step. Create web-optimized versions at specific dimensions. A 15 MB source becomes multiple outputs under 200 KB each.
Resize & CompressCompress Once, Share Everywhere
Compress images to under 1 MB and they work on every workplace platform. For Jira, Linear, and Figma comments (strictest at 4-10 MB), aim for under 500 KB per image.
Target under 500 KB for universal compatibility
At 500 KB, your image fits everywhere -- even Figma comments (4 MB) and Notion free tier (5 MB). One compression, every platform.
JPG at 90% quality keeps text readable
Converting PNG screenshots to JPG at 90% quality reduces file size by 80-95% while keeping all text, UI elements, and details perfectly readable.
Crop before compressing
Remove your dock, taskbar, and irrelevant parts of the screen. Cropping to just the relevant area can cut file size by 50% before compression even starts.
1280px width is enough for most sharing
Retina screenshots at 5120px wide are overkill. Resize to 1280px width -- still crisp on any screen, dramatically smaller file.
How to Compress Work Images with Diwadi
Download and Open Diwadi
Install Diwadi on your Mac or Windows computer. No account needed, no internet required for compression.
Drop Your Screenshots or Images
Drag and drop your screenshots, design exports, or photos into Diwadi. Supports PNG, JPG, WebP, HEIC, TIFF, BMP, and more. Drop multiple files for batch processing.
Choose Format and Quality
Convert PNG to JPG for maximum compression, or to WebP for modern platforms. Adjust quality -- 90% keeps text sharp, 80% for photos where exact detail matters less.
Share on Any Platform
Your compressed images are saved locally. Attach to Jira tickets, paste in Slack, email to clients, or embed in Confluence. They stay private throughout.
Why Compress Work Images Offline?
Screenshots Contain Proprietary Code & UI
Bug report screenshots often show internal source code, proprietary UI designs, and unreleased features. Uploading these to online compressors exposes your company's intellectual property.
Design Mockups Are Intellectual Property
Figma exports and design screenshots represent months of design work. They contain branding, UI patterns, and product roadmap details that competitors would love to see.
Client Data Visible in Screenshots
Dashboard screenshots, CRM screenshots, and analytics views often contain customer names, revenue figures, and other sensitive client data that should never leave your device.
Internal Dashboards & Metrics
Screenshots of internal tools, Grafana dashboards, financial reports, and performance metrics contain confidential business data. Keep them off third-party servers.
No Upload to Third-Party Servers
Diwadi processes every image locally on your computer. Nothing is uploaded, nothing is stored externally. Your work screenshots never leave your device.
Pro Tips for Workplace Images
Use WebP for Slack and web-based tools
Slack, Notion, Linear, and most web apps support WebP natively. WebP files are 30-50% smaller than JPG at the same quality -- your screenshots load faster for everyone.
Crop before compressing
Remove the dock, taskbar, bookmarks bar, and other irrelevant screen areas. A cropped screenshot of just the bug is more useful AND smaller than a full-screen capture.
Batch compress a folder of screenshots
After a testing session or design review, drop your entire screenshots folder into Diwadi. Compress all images at once with the same settings -- saves minutes per session.
Convert PNG to JPG for 80% size reduction
PNG screenshots are lossless and huge. Converting to JPG at 90% quality gives you an 80-95% file size reduction with minimal visible quality loss. Text stays perfectly readable.
Common Mistakes When Sharing Work Images
Sending 10 MB PNGs when JPG would do
Unless you need transparency or pixel-perfect lossless quality, JPG at 90% is visually identical to PNG for screenshots. You're wasting bandwidth and hitting platform limits for no reason.
Not cropping irrelevant screen area
Full-screen screenshots include your dock, taskbar, bookmarks, notifications, and other irrelevant content. Crop to just the relevant area -- it's smaller, more focused, and more professional.
Over-compressing so text becomes unreadable
JPG quality below 70% can make text blurry and introduce visible artifacts around sharp edges. Stick to 85-90% quality for screenshots with text -- the file is still tiny.
Using GIF for static screenshots
GIF is limited to 256 colors and produces much larger files than JPG or WebP for photos and screenshots. GIF is only appropriate for short animations -- never for static images.
Not batch processing multi-step documentation
If you're documenting a 15-step process, compress all 15 screenshots at once. Processing them one by one wastes time and leads to inconsistent quality settings across the set.
Workplace Image Sharing Checklist
- Check the target platform's image size limit before sharing
- Crop screenshots to show only the relevant area
- Convert PNG screenshots to JPG for 80-95% size reduction
- Use 90% JPG quality to keep text sharp and readable
- Resize to 1280px width for most workplace sharing
- Use WebP for Slack, Notion, and web-based platforms
- Never upload work screenshots to online compression tools
- Batch compress when sharing multiple screenshots
Frequently Asked Questions
Why are my Mac screenshots so large?
Mac Retina displays capture screenshots at 2x or 3x native resolution. A 27" iMac produces screenshots at 5120x2880 pixels, resulting in 5-15 MB PNG files. This is far more resolution than needed for sharing in Jira, Slack, or email. Convert to JPG and resize to 1280px width to reduce by 95% or more.
What's the best format for bug report screenshots?
JPG at 90% quality is ideal for most bug report screenshots. Text, error messages, and UI elements stay perfectly readable while the file drops from 5-12 MB (PNG) to 100-500 KB (JPG). If you need to show exact pixel rendering, keep PNG but crop to just the relevant area.
How do I compress a screenshot without making text unreadable?
Use JPG quality of 85-90%. At this level, text remains crisp and artifacts are invisible at normal viewing size. Avoid going below 70% quality for screenshots with text. Also, avoid resizing below 1024px width -- text becomes hard to read at very small sizes.
Can I batch compress all screenshots from a testing session?
Yes. Diwadi supports batch processing -- drag and drop an entire folder of screenshots and compress them all with the same settings. This is much faster than processing individually and ensures consistent quality across all images in your documentation.
Does Slack compress images automatically when uploaded?
Slack generates preview thumbnails but preserves the original file. Uploading a 15 MB PNG means the full 15 MB is stored and transferred. Large images load slowly in channels and use storage quota. Compress before uploading for faster previews and less storage usage.
What's the maximum image size for Jira attachments?
Jira's default attachment limit is 10 MB per file. Jira administrators can increase this in System Settings, but most organizations keep the default. A single Retina screenshot can exceed this limit. Compress to JPG to easily fit under 10 MB -- most screenshots become 100-500 KB.
Should I use PNG or JPG for design feedback?
For design feedback in Slack or Figma comments, use JPG at 90% quality. The visual difference is imperceptible at screen viewing distance, but the file is 80-95% smaller. Only use PNG if you need to show exact color accuracy (e.g., checking a specific hex value) or transparency.
How do I reduce a Figma export from 20 MB to under 1 MB?
Export from Figma as PNG, then convert to JPG at 85-90% quality using Diwadi. A 20 MB Figma export typically becomes 200-600 KB as JPG. If the design uses flat colors and simple shapes, you can go even smaller. WebP gives another 30-50% reduction over JPG.
Why does Notion reject my image upload?
Notion's free plan limits file uploads to 5 MB per file. Retina screenshots and Figma exports often exceed this. Compress to JPG or WebP before uploading -- most screenshots compress well below 1 MB. Notion's paid plans remove this limit, but compressed images still load faster.
Can I convert screenshots to WebP for smaller file sizes at work?
Yes, WebP produces files 30-50% smaller than JPG at the same visual quality. Most modern workplace platforms support WebP: Slack, Notion, Linear, GitHub, and all web browsers. The main exceptions are some older email clients and desktop apps. For maximum compatibility, use JPG. For Slack and web tools, WebP is the best choice.
Compress Work Screenshots Privately in Seconds
Diwadi compresses screenshots, design exports, and photos locally on your computer. Your proprietary work images never leave your device. Free to use.