Free · Fast · Privacy-first

Convert PNG Screenshot to JPG

Screenshots are always saved as PNG by macOS, Windows, Android, and iOS because PNG is a lossless format that preserves every pixel of interface text, icons, and sharp colour transitions exactly as they appeared on screen.

⚡

Reduce screenshot file size by 60-80%

🔒

Text and UI elements stay sharp at 88%+

✨

Instant browser-based conversion

⚡

No sign-up or watermark

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this Image Format Converter to your website

Drop the Image Format Converter into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/image-tools/image-format-converter?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Format Converter by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/image-tools/image-format-converter?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="Image Format Converter by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Why Screenshots Are Always PNG -- And When That Creates a Problem

Every major operating system defaults to PNG for screenshots because PNG is lossless and screenshots are primarily composed of text, sharp UI edges, and flat colour areas, exactly the content type where lossless preservation matters most. A JPEG screenshot taken at typical default quality settings would introduce visible blurriness in fine text and colour banding along sharp edges between UI elements, making it noticeably harder to read interface content at the original resolution. macOS Cmd+Shift+3, Windows PrtScn or Win+Shift+S through Snipping Tool, Android volume-down+power, iOS side+volume-up, and the various Linux screenshot utilities including GNOME Screenshot and KDE Spectacle all produce PNG files for this reason. The PNG format handles the repeating colour patterns and sharp transitions in UI screenshots with good compression efficiency, often producing smaller files than JPEG would for the same visual quality on synthetic computer-generated graphics.

The problem arises when screenshots need to be shared with anyone else over a constrained channel. A typical desktop screenshot at 1920x1080 resolution is 500 KB to 2 MB as PNG. A Retina screenshot at 2880x1800 or a 4K screenshot at 3840x2160 can reach 4 to 8 MB per file because the high pixel count multiplies the storage requirement even with lossless compression. Email clients have attachment size limits ranging from 5 MB on conservative corporate systems to 25 MB on Gmail and Outlook web. Slack compresses large images aggressively before displaying them which reduces quality unpredictably. Many CMS uploads have per-image size caps of 1 MB or 2 MB. Shared document platforms like Confluence, Notion, and Google Docs display images at reduced quality when they exceed a file size threshold. Converting the screenshot to JPG at 88 to 92 percent quality reduces a 2 MB PNG screenshot to 300 to 600 KB while keeping text perfectly readable, a reduction of 70 to 85 percent that fits comfortably within every platform restriction.

The right quality setting for screenshots depends entirely on the content type within the screenshot. A screenshot that is primarily text and UI chrome such as a browser window with menus, an application dialog box, or a system preferences pane should use 88 to 92 percent quality. At this range, JPG compression handles the sharp text edges well enough that the output is clean and readable at 100 percent zoom even on a high-resolution display. A screenshot that includes embedded photographs or illustrations such as a browser screenshot of a news article with a hero image, or a design tool showing a finished composition, can tolerate a slightly lower setting of 85 percent because the photographic areas mask any compression artifacts that might appear in the surrounding UI. Below 80 percent, text in screenshots develops visible blurriness and characteristic JPEG block artifacts at sharp edges, making the content harder to read and the screenshot less useful as documentation.

There is also a practical workflow argument for converting screenshots routinely as part of any shared-documentation pipeline rather than uploading the original PNGs. Many ticketing systems, internal wikis, and customer support tools display screenshots at fixed widths in their UI, typically 800 to 1200 pixels wide regardless of the source resolution. Uploading a 4 MB Retina PNG that the platform will downsample to 1000 pixels wide before display wastes bandwidth on every page load for every viewer, and triggers the platform server-side compression branch which often introduces its own artifacts. Converting to JPG at 90 percent before upload gives you control over the quality reduction step rather than delegating it to whatever the platform algorithm decides, which is the same logic that applies to social media platforms but with even more direct benefit in internal team tooling where the platform compression is rarely optimised carefully.

PNG specification and use cases (W3C)JPEG artifacts and quality (Wikipedia)Image file size and web performance (web.dev)

How to use this tool

💡

Upload your PNG screenshot and set quality to 88-92% for sharp, readable text. This range gives a 60-80% file size reduction while keeping all UI text and interface elements crisp. Ideal for screenshots destined for Slack, email, Jira, or Confluence.

How It Works

Step-by-step guide to convert png screenshot to jpg:

1
Take or locate your screenshot PNG
Find the PNG screenshot in your default screenshots folder, which varies by operating system. On macOS the default is the Desktop or a configured Screenshots folder in your home directory. On Windows the default is Pictures then Screenshots when using Win+PrtScn. On Android and iOS the file lives in the gallery or the Photos app with a corresponding entry in the Files app for direct access. If you are about to take a new screenshot, use the standard shortcut for your OS now and then continue with the next step.
2
Upload to FixTools
Open the Image Format Converter and drag the PNG screenshot directly onto the upload area in the browser, or click the upload button to select it from your file system through the standard file picker. For multiple screenshots that are all part of the same documentation set or ticket attachment, select them all at once using Ctrl on Windows or Cmd on Mac in the picker, or by dragging a multi-selection from your screenshots folder onto the converter window in a single operation.
3
Select JPG and set quality to 88-92%
Choose JPG as the output format from the format selector panel, then set the quality slider to a value between 88 and 92 percent. This range is the optimal sweet spot for screenshots that contain text and UI elements because it preserves all the sharp character edges and fine interface detail while still cutting file size by 60 to 80 percent compared to the source PNG. Push toward 92 percent if the screenshot has very small text or fine icon detail.
4
Convert and check the preview
Click Convert to run the encoding step locally in your browser, then inspect the preview at 100 percent zoom to confirm text remains sharp and readable across the whole image. Zoom in particularly on any small text such as menu items, status bar text, or fine print to make sure no character edges have developed visible blur. If anything looks soft, increase the quality by a few points and reconvert before downloading the final file.
5
Download and share your JPG
Download the converted JPG to your default Downloads folder. It will be 60 to 80 percent smaller than the original PNG and ready to attach to emails, paste into Slack messages, upload to Jira or Linear tickets, embed in Confluence or Notion documentation pages, or share through any other channel. The reduced file size means the attachment uploads faster, displays sooner for recipients on mobile data, and fits within platform per-image size limits without triggering server-side recompression.

Real-world examples

Common situations where this approach makes a real difference:

Bug reports and support tickets

A QA engineer attaches 8 to 10 annotated screenshots to a single Jira ticket documenting a complex regression bug across multiple steps of a user flow. Each PNG comes in at 1.5 to 3 MB, pushing the total attachment size over the 10 MB ticket limit enforced by the company Jira instance. Converting each screenshot to JPG at 90 percent quality through FixTools reduces them to 250 to 500 KB each, comfortably under the limit and significantly faster to load for the developer reviewing the ticket on a slow connection or a mobile device while away from the office. The annotations and arrows added in the markup tool remain crisp and readable at 90 percent quality.

Slack and team messaging

A remote team member shares a screenshot of a configuration error in a Slack channel where colleagues across multiple time zones will see it on a mix of desktop and mobile devices. The 2.4 MB PNG loads slowly for colleagues on mobile data and Slack applies its own aggressive compression on top, which sometimes blurs the error message text further. Converting to JPG at 88 percent quality first produces a 380 KB file that loads instantly for everyone, and the error message text remains completely readable at the size it displays in the Slack feed on both desktop and mobile clients without any further loss from the platform compression pass.

Technical documentation

A technical writer building a user manual for a new product release has 60 step-by-step UI screenshots, each 1 to 4 MB as PNG depending on the screen complexity. Converting all 60 to JPG at 90 percent quality in a single batch reduces the total from around 120 MB to under 20 MB without any visible quality loss in the printed manual or the online HTML version. The resulting document is a practical downloadable PDF size that customers can email and save easily, rather than an unwieldy 100 MB plus file that stalls in email gateways and triggers retries on weak corporate connections.

Email client attachments

A consultant preparing a client-facing report wants to embed 5 dashboard screenshots in an email attachment along with the written analysis. The Gmail attachment limit is 25 MB, and the 5 PNGs total 18 MB which is close to the limit with no room for the email body, the cover document, or any other supporting attachments such as a PDF summary. Converting all five screenshots to JPG at 88 percent quality brings the screenshot total to under 4 MB, leaving plenty of room for additional content within the limit and making the email reliably deliverable to corporate recipients whose inbound gateways also enforce per-message size limits.

Pro tips

Get better results with these expert suggestions:

Quality 88-92% is the sweet spot for screenshots

Below 85 percent quality, fine text in screenshots can appear slightly blurry or develop visible compression artifacts at character edges that make reading slower for the recipient. Above 92 percent, file sizes grow significantly with no visible quality improvement at normal viewing sizes that anyone would actually notice in a chat app or ticket thread. The 88 to 92 percent range preserves all readable text and UI detail while achieving the 60 to 80 percent file size reduction that makes sharing practical across email, chat, and ticketing platforms with strict per-image size limits.

Retina screenshots benefit most from conversion

Retina and HiDPI screenshots are often double the pixel dimensions of their display resolution. A 1440p display screenshot may actually be captured at 2880x1800 pixels because macOS captures at the device-pixel resolution rather than the logical resolution. These already-oversampled images can tolerate JPG compression unusually well because the high pixel density provides redundancy that masks any quantization artifacts at normal viewing scale. Converting a 4 MB Retina screenshot to JPG at 90 percent often produces a 400 to 600 KB file that is visually indistinguishable from the PNG when displayed at the actual screen size of the recipient device.

Annotate before converting, not after

If you add annotations such as arrows, highlight boxes, and text callouts to your screenshot using a markup tool like Skitch, Snagit, Markup on macOS, or the iOS Markup feature, do this work on the PNG before converting to JPG. Annotation tools typically save back to PNG and preserve your edits losslessly through any number of revisions. Converting to JPG after annotation ensures the final output is exactly one generation of JPEG compression, not multiple re-compressions of an annotation layer that would compound quality loss with every save during the markup process.

Crop before converting to remove unnecessary areas

Use the FixTools Image Cropper or the built-in crop tool in your screenshot utility to remove taskbars, browser chrome, irrelevant screen areas, and any visible parts of unrelated applications from your screenshot before converting to JPG. Removing even 20 percent of the image area reduces the file size proportionally before compression even runs, and a tighter crop also makes the actual content much easier to read in the receiving platform without the recipient needing to zoom or scroll. A cropped screenshot is also more focused as documentation, drawing attention to the relevant interface element.

FAQ

Frequently asked questions

Operating systems save screenshots as PNG because screenshots primarily contain text, UI elements, icons, and sharp-edged graphics, content that JPEG handles poorly at typical quality settings because the DCT compression algorithm at the heart of JPEG cannot efficiently represent step changes in colour or brightness. JPEG lossy compression introduces blurring and characteristic 8-pixel block artifacts around sharp edges and fine text, making screen content harder to read in the resulting file. PNG preserves every pixel exactly through its lossless DEFLATE compression, which is the right default for screenshots intended to document interface states accurately for bug reports, support tickets, or technical documentation where accuracy matters more than file size at capture time.

Use 88 to 92 percent quality when converting screenshots that contain text, interface elements, icons, or sharp graphics of any kind. This range preserves text readability while reducing file size by 60 to 80 percent compared to the source PNG, which is the meaningful win for sharing through any constrained channel. Below 85 percent, fine text at small point sizes can develop visible blurriness at the character edges that makes reading slightly slower for the recipient and looks visually rough at 100 percent zoom. Above 92 percent, file sizes increase significantly without any visible quality improvement for typical sharing and documentation purposes on standard viewing devices.

A typical 1920x1080 desktop screenshot converts from 500 KB to 2 MB PNG to approximately 120 to 400 KB JPG at 90 percent quality, which is a reduction of 60 to 80 percent depending on screen content complexity. A 2560x1440 or higher Retina screenshot might go from 3 to 6 MB PNG to 400 to 900 KB JPG at the same quality setting. Mobile screenshots at 1080x1920 typically reduce from 800 KB to 2 MB PNG down to 150 to 350 KB JPG. Results vary based on the proportion of flat colour areas, sharp edges, and text in the screenshot, with text-heavy screenshots compressing less efficiently than mixed-content screens.

Yes, at quality settings of 88 percent and above the text remains fully readable for any standard system font size used in modern interfaces. JPEG handles text in screenshots adequately at high quality settings because the high pixel density of modern displays, especially Retina and HiDPI screens, provides enough redundancy that minor quantization effects are invisible at normal viewing sizes. Inspect your converted screenshot at 100 percent zoom rather than fitted-to-screen to confirm text legibility before sharing. The 100 percent view shows the worst-case quality impact, and if text looks fine there it will look fine in any real-world viewing context.

Yes. FixTools supports batch upload of multiple PNG files in a single operation. Select all your screenshots using Ctrl+A on Windows or Cmd+A on Mac in the file picker, or drag a multi-selection from your screenshots folder directly onto the upload area. Set quality to 90 percent for the whole batch and convert all the files at once with consistent settings applied uniformly. Download the results as a ZIP archive ready for upload to your documentation platform or ticket attachment. This is the most efficient approach for processing a folder of documentation screenshots from a feature release in one operation rather than opening each file individually.

At quality settings of 88 percent and above, colour accuracy in screenshots is well preserved across the full range of typical interface colours. JPEG chroma subsampling can theoretically cause minor colour shifts in very saturated UI elements such as bright reds and pure greens, but at high quality settings these shifts are imperceptible in practice for normal viewing. For screenshots used in technical documentation where exact colour accuracy is required, such as documenting colour-coded status indicators in a monitoring dashboard or design system colour swatches, use 92 percent or above to give the chroma subsampling enough headroom to preserve every visible colour distinction at full fidelity.

Convert PNG screenshots to JPG at 88 to 90 percent quality before uploading to Slack rather than uploading the raw PNG and letting the platform handle the conversion. This prevents Slack from applying its own server-side compression to your image with no input from you on the quality parameter, which can reduce quality unpredictably depending on the source file size and the current platform compression policy. A JPG screenshot in the 150 to 400 KB range loads instantly in the Slack feed on both desktop and mobile clients, and the text remains sharp at the size it displays in the chat window across every device the recipient might be using.

Yes, Retina and 4K screenshots benefit significantly from JPG conversion because they are the largest files in absolute terms and have the most redundancy to compress away. They are often 3 to 8 MB as PNG and display on most screens at half their actual pixel dimensions or smaller, which means the recipient never sees the full pixel detail anyway. Converting to JPG at 90 percent typically reduces them by 75 to 85 percent while maintaining full visual quality at any practical viewing size. The high original resolution provides enough margin that JPEG compression has minimal perceptible impact even on the recipient most discerning displays.

No, annotations such as arrows, highlight boxes, text callouts, and crop marks added through markup tools are part of the pixel data once the annotated PNG is saved, so they convert to JPG along with everything else in the image. At quality settings of 88 percent and above, annotation elements with sharp edges and solid colours remain crisp and readable. The thin lines of arrows and boxes are the most sensitive elements to JPEG compression, so if you have very thin one-pixel annotation lines and you are converting at a quality below 90 percent, inspect the result at 100 percent zoom to confirm the lines have not blurred or developed visible fringing along their edges.

You cannot recover the original PNG quality from a JPG once the conversion has happened, because JPEG compression discards data during encoding and that data cannot be reconstructed by any subsequent processing step. Converting the JPG back to PNG using FixTools creates a lossless container around the already-compressed JPEG pixel data, which is useful if you want to do further annotation or editing without compounding compression loss, but it does not restore the lost quality. This is why the standard recommendation is to keep your original PNG screenshots in an archive folder and treat the JPG as a deliverable copy rather than your master file.