ShareX Screenshots Saving in the Wrong Format: How to Fix PNG, JPG, and GIF Output

If ShareX screenshots are saving in the wrong format, the cause is usually not the capture tool itself. The unexpected output often comes from the selected image file format, an after-capture conversion step, an image effect, or confusion between clipboard data and the file saved to disk. A filename may also display the extension you expected while the underlying image is encoded differently.

The safest way to troubleshoot this problem is to test one ordinary screenshot with a save-only workflow. Once that file saves in the correct format, quality, and transparency mode, re-enable editing, effects, uploads, and automation one step at a time. This isolates the setting responsible without disrupting an otherwise useful ShareX configuration.

1. Confirm the Symptom and Reproduce It With a Simple Test

Begin by identifying exactly what is wrong. Format problems can look similar while requiring different fixes. For example, a screenshot may have a .png extension but contain a solid background where transparency was expected. A JPG may be correct technically but appear blurry because of its quality setting. A GIF may be animated when you expected a static image, or a recording may use an entirely different output setting from still screenshots.

1.1 Inspect the actual saved file

Take a new screenshot and save it locally. In File Explorer, right-click the file, choose Properties, and inspect its file type and extension. You can also open it in an image editor or browser that reports the detected format.

Make sure Windows displays filename extensions:

1. Open File Explorer.
2. Open the View menu.
3. Enable File name extensions. Depending on the Windows version, this option may appear under View and then Show.
4. Inspect the complete filename, including its final extension.

This can expose names such as screenshot.png.jpg or screenshot.jpg.png. Windows may hide the final extension by default, making a renamed file look as if it changed formats when it did not.

Success means that you can see the full filename and distinguish the expected extension from the file's actual type. If both are already correct, concentrate on quality, transparency, or workflow processing rather than renaming.

1.2 Use a diagnostic image

For a useful test, capture a small area containing text, a photograph, and a window edge. If transparency matters, use a capture method or editor operation that can genuinely produce transparent pixels. An ordinary rectangular screen capture normally records the visible desktop behind the selected content, so it does not automatically become transparent merely because it is saved as PNG.

Compare the result against these common symptoms:

• Wrong extension: The file ends in JPG, PNG, GIF, or another extension you did not select.
• Poor quality: Text edges or interface details show JPEG artifacts.
• Unexpected file size: A screenshot is much larger or smaller than comparable captures.
• Lost transparency: Transparent areas become white, black, or another solid color.
• Wrong animation behavior: A GIF is static, or a screen recording is produced instead of a still image.
• Clipboard mismatch: Pasting produces different quality or transparency from opening the saved file.

Do not change several options yet. First reproduce the same symptom twice. A consistent result usually points to a setting or task, while an intermittent result may indicate different hotkeys or workflows.

2. Check the ShareX Settings Directly Related to This Problem

2.1 Verify the image file format setting

Open ShareX and find Task settings, then inspect the Image settings. Look for the image format or file format selection. ShareX interface labels can vary as the application evolves, but the relevant setting controls how still screenshots are encoded when they are saved.

Select the format you actually need:

• PNG: Best for interface screenshots, text, diagrams, sharp edges, and transparency. PNG uses lossless compression, although optimization settings can affect file size and processing time.
• JPG or JPEG: Often smaller for photographs and complex scenes. It uses lossy compression, does not preserve transparency, and may create visible artifacts around text.
• GIF: Supports animation and limited transparency, but its restricted color palette makes it a poor default for many full-color still screenshots.

Take one new screenshot after selecting the format. Existing files will not be converted automatically. Success means the new saved file uses the selected encoding and extension. If it does, stop changing the core image setting and investigate only the workflow that previously produced the wrong result.

2.2 Adjust JPG quality without confusing it with format

Choosing JPG determines the file format, while the JPEG quality control determines the compression level. A lower quality value generally reduces file size but increases visible artifacts. This is particularly noticeable in screenshots containing small text, icons, and flat-color interface elements.

If the extension is correct but the image looks degraded, raise the JPEG quality and capture the same area again. If clarity is more important than file size, switch to PNG instead. Repeatedly renaming .jpg to .png will not restore detail lost during JPEG compression.

Success means the test JPG has acceptable detail at a practical file size. Once it meets your requirement, stop adjusting quality. There is no need to troubleshoot capture permissions, networking, or upload services when the file itself is being created correctly.

2.3 Understand PNG transparency limits

PNG can store transparent pixels, but selecting PNG does not create transparency by itself. The captured or edited image must contain transparent areas. If an after-capture process flattens the image onto a background, those pixels may no longer be transparent by the time the file is saved.

If transparency disappears, disable image effects and conversion steps temporarily. Save the unprocessed image as PNG and inspect it in an editor that displays transparency with a checkerboard. Do not rely solely on an image viewer with a white background, because transparent pixels can look white there even when the alpha channel remains intact.

Success means the PNG retains transparent pixels when opened in a transparency-aware editor. If that works before effects but not afterward, the effect chain is the relevant problem.

2.4 Review after-capture tasks

After-capture tasks run after ShareX obtains the image. A workflow may add effects, open the editor, copy the image, save it, upload it, or perform another action. If one of those steps converts or re-encodes the image, its output can override your expected result.

Temporarily review the active after-capture tasks and disable anything that could alter image data, especially:

• Add image effects
• Open in image editor
• Custom conversion or external program actions
• Automation that renames or re-encodes files
• Tasks that create a derived image for upload

Leave only the task that saves the image to a file. Capture a new screenshot. If the format is now correct, re-enable the disabled tasks individually and test after each one. Stop when the unwanted format returns. The last enabled task is the likely cause.

2.5 Inspect image effects and their output behavior

Image effects can do more than add borders or watermarks. Depending on the configured effect chain and output behavior, processing may flatten transparency, alter color information, or create a new output file. An effect involving a background, canvas, shadow, border, or image overlay deserves particular attention when transparency changes.

Open the active image-effects configuration and check for any format-related output option. Also look for effects that place the image on an opaque canvas. Disable the effect chain and test again before deleting it. If the clean PNG preserves transparency, modify or duplicate the effect preset rather than changing unrelated ShareX settings.

3. Check Windows and Workflow Factors

3.1 Separate clipboard content from the saved file

The image placed on the Windows clipboard is not necessarily a byte-for-byte copy of the saved PNG, JPG, or GIF. Clipboard image data may be supplied in one or more Windows bitmap-oriented formats, and the receiving application decides how to interpret, flatten, compress, or save it.

For example, pasting a transparent PNG into an application that does not preserve alpha transparency can produce a solid background. A messaging or document application may also recompress a pasted screenshot even when the ShareX file is a valid PNG.

Test the saved file directly:

1. Use ShareX to save a screenshot as PNG.
2. Open that file from disk in a suitable viewer or editor.
3. Separately paste the clipboard image into the destination application.
4. Compare the two results.

If the disk file is correct but the pasted version is not, ShareX's saved-file format is working. Adjust the receiving application or insert the saved file instead of pasting. Stop changing ShareX's image format because it cannot force every clipboard recipient to preserve the same representation.

3.2 Do not change an extension to convert a file

Renaming capture.jpg to capture.png changes only the name. It does not convert JPEG data into PNG data, restore transparency, or remove compression artifacts. Some programs inspect the file contents and open it anyway, while others report that the file is invalid or uses an unexpected format.

To convert an existing file, open it in a trusted image editor and use Save As or Export. To fix future captures, select the desired format in ShareX and remove any later conversion task.

3.3 Make sure the same hotkey uses the workflow you tested

ShareX can associate different hotkeys with different tasks. A region capture hotkey, active-window capture, screen recording, and custom workflow may not produce equivalent output. If one hotkey saves PNG while another saves JPG, compare their task settings or per-hotkey overrides.

Test by launching the same capture command directly from the ShareX window. Then test the problematic hotkey. If only the hotkey fails, inspect that hotkey's task configuration rather than changing the global format repeatedly.

3.4 Distinguish still-image settings from recording settings

A screen recording workflow is different from an ordinary screenshot workflow. Animated GIF output, video output, frame rate, and recording encoders are controlled through recording-related settings. Changing the still-image format to GIF does not necessarily make a screen recording workflow save an animated GIF, and changing recording output does not determine the format of ordinary screenshots.

If the problem occurs only during recording, verify that you launched the intended screen recording or GIF recording command. If it occurs during a single-frame capture, return to the image format and after-capture settings.

Display scaling can influence capture dimensions, but it does not normally change PNG into JPG. Audio settings apply to recordings, not still-image encoding. Network and upload settings can affect remote copies or links, but they do not explain a wrong local file format when the save-only test succeeds.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test prevents editors, uploads, effects, and custom actions from obscuring the result. You do not need to erase your configuration. Record the current task selections or export your settings if appropriate, then make only temporary changes.

1. Select PNG as the still-image format.
2. Disable image effects and custom post-processing.
3. Disable upload tasks for this test.
4. Disable clipboard-only behavior if it prevents a local file from being created.
5. Enable only the after-capture task that saves the image to a file.
6. Capture a small region from the ShareX interface.
7. Inspect the saved file's full extension and actual format.

If the PNG test succeeds, repeat it with JPG. Check the extension and visual quality. If needed, perform a separate GIF test using the correct still-image or recording workflow for your intended result.

Success means each new file matches the format selected for that specific test. At that point, the encoder and basic save process work. Re-enable one workflow feature at a time. Do not reinstall ShareX or modify Windows permissions unless the minimal test cannot create or open the file at all.

If the minimal test still produces the wrong format, check for per-hotkey task overrides, portable versus installed configurations, and whether you are opening the newest file. Sorting the destination folder by Date modified can prevent an older capture from being mistaken for the latest test.

5. Check History, Logs, and Recent Workflow Output

ShareX history can help confirm what task ran and which local file or uploaded result belongs to a capture. Open the history or recent task information and locate the test by timestamp. Verify that the file path and filename match the item you inspected.

Pay attention to task notifications and error messages. A conversion tool or custom action may fail, leaving an earlier intermediate file behind. Conversely, an upload destination may convert an image after upload even though the local ShareX file is correct. Compare the local file with the downloaded remote copy before blaming the capture format.

If ShareX reports an error, preserve the exact message. Review the application's debug log through the available debug or log option in your installed interface. Useful clues include the task name, output filename, external command, and timestamp. Avoid posting logs publicly without checking them for file paths, account details, upload URLs, or other sensitive information.

Logs are most useful when the wrong output is caused by an external program, script, plugin, or failed task. If ShareX saves a valid local PNG in the minimal workflow, there is little value in changing permissions or reinstalling the application. The evidence already shows that the basic capture and encoder are working.

6. Quick Fix Checklist

• Enable filename extensions in File Explorer and inspect the complete filename.
• Choose the intended still-image format in ShareX Task settings.
• Use PNG for lossless interface captures and transparency.
• Use JPG for photographic content when smaller files justify lossy compression.
• Adjust JPEG quality if JPG files look blurry or blocky.
• Do not expect PNG selection alone to create transparent pixels.
• Temporarily disable image effects that flatten or reprocess the image.
• Disable custom conversions and leave only Save image to file active.
• Compare the saved file with clipboard output instead of assuming they are identical.
• Never rename an extension as a substitute for conversion.
• Check whether the problematic hotkey has its own task settings.
• Use recording settings for animated GIF or video workflows.
• Test one new capture after every change.
• Stop changing settings as soon as the minimal saved file is correct.

7. Frequently Asked Questions

7.1 Why does ShareX save JPG when PNG is selected?

An after-capture task, image effect, custom action, or per-hotkey override may be producing the final JPG after the initial capture. Disable processing tasks and test with only Save image to file enabled. Also inspect the full extension and make sure you are opening the newest file.

7.2 Why does my PNG have a white background?

PNG supports transparency, but the image must contain transparent pixels. A standard screenshot records visible pixels, including the desktop or window behind an object. Image effects, editors, and clipboard recipients can also flatten transparency onto a white background. Open the saved PNG in a transparency-aware editor to determine whether the alpha channel is truly missing.

7.3 Why does a pasted screenshot look different from the saved file?

The clipboard can provide image data differently from a saved PNG or JPG, and the receiving application controls how pasted data is processed. It may flatten transparency or recompress the image. If the file from disk is correct, attach or insert that file rather than pasting.

7.4 Can I convert JPG to PNG by changing the extension?

No. Renaming the extension does not change the internal encoding. Use an image editor's Save As or Export function. Converting an already compressed JPG to PNG will prevent additional JPEG loss during that save, but it cannot restore detail previously discarded.

7.5 Why is ShareX creating a static GIF instead of an animated GIF?

A still-image capture saved as GIF contains only a single frame. For animation, start the appropriate screen recording or GIF recording workflow and check its recording output settings. Still-image format selection and screen-recording format selection serve different tasks.

7.6 Should I reinstall ShareX when the format is wrong?

Usually not. First run the save-only test with effects, uploads, editors, and custom actions disabled. If that test produces the correct format, the installation is functional and the cause is in the workflow. Consider configuration repair or reinstallation only after the minimal test fails consistently and you have ruled out per-hotkey settings and configuration differences.