PNG Compressor

PNG Compressor needs different expectations from a JPEG compressor because PNG is a lossless format. Screenshots, UI captures, logos, diagrams, and graphics with sharp edges can already be efficiently encoded, so saving the same pixels as PNG again may produce little reduction or even a larger file. The tool therefore separates the desire to keep PNG from the desire to obtain the smallest possible result.

Choose explicit PNG output when the file must remain PNG. That path preserves lossless PNG behavior, but it cannot guarantee meaningful savings. When Same as original is combined with active compression, the current workflow may use WebP where that creates a genuinely smaller result. JPG or WebP can also be chosen explicitly when the destination accepts a lossy or different modern format. Pixel dimensions are not reduced by this compressor.

An optional Target KB value can express the upload goal, but the target is still constrained by the source. A large, detailed, or noise-heavy PNG may not reach a strict limit without a format change or fewer pixels. For graphics that rely on transparent areas, consider the destination format carefully because JPG cannot preserve alpha transparency.

The source is processed locally in the browser. Use the general Image Compressor for mixed-format batches. Use Image Resizer when a hard size limit cannot be met through encoding alone and changing width or height is acceptable. The dedicated 100KB and 200KB routes are better when a form names one of those limits directly.