trsh

Troubleshooting

Fix common image compression problems

A smaller setting does not always produce a smaller or better image. Use the symptom below to find a practical next step, then compare the exported file against your original.

The compressed file is larger than the original

This can happen, especially when converting a photograph to PNG. PNG uses lossless encoding, and a photo’s many colors and subtle details can be inefficient to represent that way. Re-encoding an already optimized image can also add overhead without saving much.

  • For a photograph, try WebP or JPEG instead of PNG.
  • For a logo, screenshot, or image that needs transparency, PNG may still be the right choice even if it is larger.
  • Reduce pixel dimensions if the image will be displayed smaller and you do not need the full resolution.
  • Compare the output size shown by the tool with the original before downloading or uploading.

The image looks blurry, blocky, or has banding

These are signs that compression or resizing removed detail. Fine text, hair, fabric, gradients, and sharp edges can show damage before a casual preview does.

  • Raise the visual quality setting, or choose a less aggressive target-size limit.
  • Use a larger maximum dimension to avoid unnecessary downscaling.
  • Try PNG for sharp text and graphics; if you lower PNG quality in trsh, remember that it quantizes colors and can alter the image.
  • Start again from the original file rather than repeatedly compressing a previously compressed export.

The output did not meet my target size

Target-size mode searches a range of qualities and can optionally reduce dimensions, but it cannot guarantee that every image fits every target. A detailed, high-resolution photo may need more reduction than a simple graphic. If the result says the target was not reached:

  1. In Advanced Tuning, check that dimension downscaling is allowed.
  2. Choose a smaller maximum dimension if the receiving site does not require the original pixel size.
  3. For a photograph, compare WebP and JPEG outputs. For transparent graphics, WebP or PNG may preserve transparency; JPEG will not.
  4. If the target is extremely small, consider whether the image can remain legible at that size. The portal’s cap may not be achievable without visible quality loss.

Transparency turned white

JPEG has no alpha transparency. When the compressor exports JPEG, transparent regions are filled with white. Choose PNG or WebP to retain transparency, and confirm that the receiving app accepts that format. More in the format comparison guide.

The image will not load or compression fails

The compressor accepts JPG/JPEG, PNG, and WebP. The interface allows files up to 100 MB, but decoding also depends on pixel dimensions and your browser/device: the current processing worker rejects images over 12,000 pixels on either side or 40 million total pixels. A modest-size file can still contain a very large pixel count.

  • Check the file extension and try a supported format.
  • Try a smaller copy or resize the image in an app that can open it.
  • Close other heavy tabs or try a current browser if the page becomes unresponsive.
  • If the original file is damaged or uses an unsupported encoding variant, try exporting a fresh copy from the app that created it.

The file is smaller, but the website still rejects it

File size is only one upload rule. Check the required extension, pixel dimensions, aspect ratio, color/background, and whether the portal’s size cap is strict. Leave a little size margin and use the exact format requested. For a 200 KB limit, follow the upload-size guide.

Keep an untouched original. Compression can change quality, dimensions, transparency, and metadata. This tool does not inspect or explicitly remove every metadata field; if metadata removal is important, verify the exported file with a trusted method before sharing it.