[New] Image Compressor in KB and Converter in online for free

What this tool does

The page accepts JPG, JPEG, PNG, GIF, WebP, JIFF and BMP files. Each queued item gets its own card with the original thumbnail, file size, pixel dimensions and a Process button. You can process one card at a time or send the whole queue together.

Conversion runs on the server. The browser reads a local preview so you can confirm that you picked the right file, then sends the image to the processing endpoint. The finished image comes back as a data URL, which powers the preview and the download link. The temporary server copy is removed after the response is encoded.

The settings panel applies to every item in the queue. If you need different formats for different files, process one group, change the settings, then add the next group. There is no per-card settings override.

Formats and when to use them

JPG and JPEG are the safe choice for photographs, especially when the destination expects a small, universally readable file. PNG is better for screenshots, diagrams and images with sharp edges or transparency. WebP is a modern web format that often produces a smaller file than JPG at a similar visual quality. GIF is useful for simple graphics and short animations, while BMP is an uncompressed bitmap that mainly survives in older Windows software.

The format menu also lists JFIF, JIFF and SVG in the interface. Treat those as advanced choices: JFIF and JIFF are closely related to JPEG, and SVG is a vector format rather than a normal raster photo. For predictable results, stay with JPG, PNG, GIF, WebP or BMP.

Choosing Keep Original leaves the format unchanged and still applies the quality, resize and DPI settings where the output format supports them. That is useful when you only want to shrink an image, not change its extension.

What the quality slider really changes

For JPG and WebP, quality controls lossy compression. A value of 75 is a reasonable default for photographs: it usually trims a lot of data without obvious damage at normal viewing size. Lower values create smaller files but can introduce blocky patches, colour banding and soft edges. Higher values preserve more detail and increase the file size.

For PNG, the same slider is mapped to compression effort rather than visual loss. PNG remains lossless, so moving the slider does not remove pixels or detail. A lower setting may compress more aggressively and take longer, but the visible image should stay the same. For BMP, compression is not the point at all; the format is normally stored without the kind of lossy compression the slider controls.

There is no setting that guarantees zero quality loss when the source is already a JPEG. Every decode and re-encode can change the pixels slightly. The tool reports the output size and the percentage difference so you can judge the trade-off instead of trusting a label.

Resize units and DPI

The Resize Unit menu offers pixels, percent, inches, centimetres and millimetres. After you choose a unit, width and height fields appear. Enter both dimensions when you want a specific box. Percent is useful for a quick reduction, while physical units are convenient when a printer or form specifies a size in inches or centimetres.

DPI is a separate field. It writes a dots-per-inch value into the output metadata and is mainly relevant to printing. Changing DPI does not automatically change the pixel width or height, and it does not make a low-resolution photo sharper. If a portal asks for both pixel dimensions and DPI, set them deliberately rather than assuming one controls the other.

Resizing and compression interact. Downscaling first often produces a smaller file than compression alone, while enlarging a small image adds pixels without adding real detail. Start with the size the destination actually needs.

Queue, URL input and batch processing

The upload area accepts multiple files. Each selected file appears in the queue, where you can remove it, process it individually, or use Process All to send the pending items in one request. The queue also reports how many files are waiting and shows a progress bar while the server works.

The From URL button opens a text area that accepts one image address per line. This is handy when the source image is already online, but it depends on the remote server allowing the fetch. A login-protected image, a hotlink blocker or a slow host can make a URL fail even though the same file works when downloaded and uploaded.

The server accepts files up to 10 MB each. There is no visible per-batch count in the interface, but very large batches still consume time, memory and request capacity. For a long list, split the work into smaller groups and confirm the output after each group.

Step-by-step use

First choose the output format. Leave it on Keep Original if you only want compression. Set a quality level, then decide whether to resize or enter a DPI value. If you are unsure, begin with quality 75, no resize, and no DPI.

Add the images by dragging them into the upload box, browsing for them, or pasting URLs. Check the queue cards to make sure the correct files are present. Press Process on one card for a test, or Process All when the settings are right for every file.

When processing finishes, compare the original and output badges. The output card shows the new file size, dimensions, DPI when supplied, and extension. Use Download to save the data URL, or Copy Base64 when you need to embed the image in code or another tool.

Limits, privacy and common surprises

This is a conversion and resizing tool, not a cropping tool. It does not remove backgrounds, straighten horizons, flip, rotate, annotate or check whether a photo meets a passport rule. Use an editor for those jobs, then return here for the final format and size.

Images are uploaded to the server for processing, so do not submit identity documents, private medical images or confidential client work unless you are comfortable with that transfer. Local previews stay in the browser, but the conversion itself is not browser-only.

A file can grow after conversion. PNG and BMP outputs are often larger than the source JPG; WebP and JPG can also grow when the original was already heavily optimized. The arrow and percentage beside the output size tell you which way the file moved. If size is the priority, try a lower quality, a smaller resize, or a different format.

Practical workflows

For a website, convert photographs to WebP or a well-compressed JPG and keep the pixel width near the size used on the page. For an email attachment, reduce the longest side and use JPG quality around 70 to 80. For a screenshot that contains text, PNG is usually the better choice because sharp edges survive without JPEG ringing.

For an older Windows application that insists on BMP, convert only the files that need it and expect much larger downloads. For a document portal that asks for a JPG, convert a PNG only after flattening transparency onto the background colour the portal expects.

Keep an untouched copy of the original. Conversion is a one-way operation in this interface, and repeated re-saving of a lossy file gradually removes detail. Work from the best source you have, not from a previously compressed copy.

Frequently Asked Questions