IGCOMPRESSOR makes a new still-image copy inside your browser. Choose a social preset, a file-size cap or Custom settings, then inspect the crop and downloaded file. Preparing a copy here and publishing it to Instagram, WhatsApp or another service are separate actions. The receiving service controls its own processing.

1. Open a file on your device

Your browser decodes supported images locally. JPEG, PNG and WebP are usual inputs, but successful decoding depends on the file and browser. HEIC support varies by device and browser. If it fails, export a JPEG from your photo app; Apple explains the available conversion options.

RAW handling extracts an embedded JPEG preview using a decoder loaded on demand. It is not a full RAW development workflow, and the preview's resolution and availability depend on the camera file. Animated inputs produce a still image; the tool does not export an animation or video.

Processing uses a Web Worker where the browser supports the required APIs, with a main-thread fallback. Ordinary page resources and advertising can make network requests, but your selected image is not sent to an image-processing endpoint.

2. Choose a crop or keep the whole frame

Exact-size presets select a ratio and crop around the position you choose in the preview. Drag the photo or use the crop-position slider to protect a face, lettering or product edge. Different placements can require different copies from the same original.

Fit within keeps the whole frame and scales it to fit the chosen bounding box. Keep original pixels skips that resize. Neither option adds a border. Exact size (crop) can enlarge a small source in Custom and form workflows, but more pixels do not recreate missing detail. Check the actual output dimensions, especially when also using a byte cap.

A social preset is an IGCOMPRESSOR export choice unless an official source establishes a requirement. It cannot reserve the crop a platform will display on every device.

3. Resize and inspect detail

For a large reduction, the pipeline halves both dimensions while both are more than twice their targets, then draws the final size with the browser's high-quality smoothing setting. This describes the implementation, not a benchmark against a desktop editor or a guarantee that every browser gives identical pixels.

Keep a master and inspect the delivery copy at its intended display size. Read small labels, check thin lines and look for an unwanted crop. A smaller image can need a different composition rather than stronger sharpening.

4. Adjust sharpening after the resize

The pipeline applies a small unsharp mask to the resized pixels. Sharpening raises local edge contrast; it cannot reconstruct missed focus, remove noise or recover texture that the source lacks.

Use Off, Light, Medium or Strong in the controls. Medium uses the preset amount where one exists. Compare restrained settings while keeping dimensions, crop and encoding quality unchanged. Stronger outlines or noise are reasons to reduce sharpening. Custom has its own visible Sharpen selector; Instagram and Exact size offer the segmented controls under More options.

The comparison view is a visual aid. Its Before image is a generated reference of the same crop and output dimensions with sharpening off, not the untouched original file. Keep the original and compare downloaded files in a suitable viewer when you need a controlled pixel-level check.

5. Choose quality or a byte cap

Without a cap, Custom uses the chosen encoding quality. With a cap, the tool searches for a fitting JPEG or WebP and can reduce dimensions when necessary. Locked dimensions may prevent reaching the cap; check the warning and download properties rather than assuming every combination is possible. PNG does not use a lossy quality slider here, although a cap can still require fewer pixels.

The Instagram presets' 500 KB to 1 MB budgets are local export choices. They are not a verified platform acceptance range or evidence that a bigger file triggers heavier compression. A quality setting is also not a percentage of original detail retained.

A minimum-size option can add JPEG comment segments without changing decoded pixels. That only increases bytes. It does not improve quality or certify that a form accepts the file. Check your notification and the current form for dimensions, size range, pose and other requirements.

6. Export, check and share

Choose JPEG, PNG or WebP where supported by the browser. Only PNG output here preserves existing transparency; JPEG and WebP flatten it onto white. The browser performs the final encoding, so this site does not promise a universal JPEG subtype, identical output bytes or preservation of a source HDR appearance. The HTML canvas standard describes browser-controlled export.

The new raster export does not copy the source photo's EXIF fields such as camera details and GPS. This is not a redaction tool: visible text and identifying features remain in the pixels, and a filename can still reveal information.

Download one file or a locally assembled ZIP. On compatible devices, Share opens the system share sheet; the apps offered depend on your device. Selecting a destination transfers the file separately under that service's rules.

Offline use and limits

Wait for the offline-ready message before relying on cached pages and core tools without a connection. A first RAW decode still needs its decoder downloaded. Offline readiness does not mean every page and optional resource has been saved.

This tool cannot stop a service from cropping or re-encoding, guarantee sharp delivery, fix exposure or color, remove a background, or recover missing detail. Keep the master, inspect the download and check the published or received result separately.

Try it on your own photoSocial-ready photos, smaller files, nothing uploaded
Compress a photo

Implementation and source review: 20 October 2026. This page describes the current local pipeline and its limits; it is not a cross-platform upload benchmark.