What changes
JPG removes transparency and is lossy. PNG encodes the decoded pixels losslessly, not the original file bytes or colour profile; it can be larger. WebP and AVIF support transparency, but the destination must accept them.
Convert image formats
Convert JPG, PNG, WebP, HEIC, HEIF and AVIF images locally. Export to JPG, PNG, WebP or AVIF without uploading files.
Runs locallyNo uploadYou control saved copies
Original dimensions are kept. If WebP or AVIF hits a memory limit, choose a smaller output here and run the tool again.
The file stays on this device. Codec engines load only after you start.
Convert real image bytes—not just the extension
The converter decodes JPG, PNG, WebP, HEIC/HEIF or AVIF and encodes a new JPG, PNG, WebP or AVIF file. The output signature is checked before the download is shown.
For a reliable result
- Choose an image and let the browser identify its decodable format.
- Select an output format. Keep original dimensions or explicitly choose a 1920/1280-pixel limit under Output size.
- Verify dimensions, transparency and visual quality in the result.
Check the download
Use the format explicitly accepted by the destination. Renaming `.heic` to `.jpg` is not conversion and is intentionally not offered.
Know before processing
HEIC, AVIF and WebP compatibility encoding can need substantial working memory even for a small file. Try a smaller Output size or JPG/PNG when encoding exceeds the budget; a source-opening limit still requires a smaller input.
Quick answers
- Can I convert HEIC to JPG by renaming the extension?
- No. Renaming changes only the filename. This tool decodes the original pixels and creates a new file with a valid signature for the selected output format.
- Which output should I use for transparency?
- Use PNG when exact transparency and broad compatibility matter. JPG cannot store transparency; WebP and AVIF can be smaller when the destination accepts them.
Choose an image format by compatibility, transparency and detail
Image conversion decodes the source picture and encodes a new file in your chosen format. This page accepts JPG, PNG, WebP, HEIC/HEIF and AVIF inputs, with JPG, PNG, WebP and AVIF outputs. Changing a filename extension alone would not perform this conversion.
Choose a format for the destination and the image, not only for the smallest possible file. A photograph, transparent logo and text screenshot have different needs. Review the exported picture because lossy encoding, transparency handling, orientation and colour conversion can affect what the recipient sees.
Select the output that preserves what matters
| Your situation | Recommended approach |
|---|---|
| A recipient requests JPG | Choose JPG and review quality. It is a lossy format without transparency; transparent source areas are filled with white. |
| Sharp screenshot text or transparency is important | Try PNG. It applies lossless encoding to the decoded pixels, but photographic images may produce much larger files. |
| A modern destination accepts WebP | Compare a WebP export at a suitable quality with the source. It can preserve transparency, but acceptance and output size still need checking. |
| You want to try AVIF | Expect an additional codec download and a potentially longer encode. Compare actual quality and size rather than assuming AVIF is always the smallest suitable output. |
Convert the sample PNG into a WebP
The 1200 × 800 document-photo.png sample contains text and colour blocks, making edge quality easy to compare after conversion.
- Choose document-photo.png and set Output format to WebP.
- Set Quality to 90% and select Convert image. No resize setting is required for this conversion.
- Confirm that the result identifies PNG to WebP and retains dimensions of 1200 × 800.
- Download the WebP and open it in the intended destination or viewer. Compare the small text and coloured edges against the source at the same zoom.
Expected result. The result is an encoded WebP file with the sample's dimensions. Pixel values and byte size can change because this quality setting is lossy. A format conversion does not imply a smaller file or byte-identical image data.
Check the downloaded result
- Confirm both the reported output format and its ability to open in the recipient's application. A file that works in your browser may still be rejected by an upload form.
- Inspect small text, gradients and fine edges. Higher quality can reduce encoding damage but cannot restore detail already lost in a previous JPG or WebP.
- Check transparent regions against both light and dark backgrounds where relevant. A white preview can hide the difference between transparency and an opaque white fill.
- Compare orientation, dimensions and metadata expectations. The conversion rebuilds the picture without copying recognized source metadata containers, which may remove information needed for your archive.
Troubleshooting
- The converted file is larger than the original
Different formats and quality settings encode the same picture differently. PNG photographs and high-quality conversions can increase size.
Try this: Compare suitable formats or use Image compressor if you have a byte ceiling. Keep the version that meets quality and compatibility needs rather than assuming conversion must shrink it.
- The background is white instead of transparent
JPG does not store transparency and the converter fills its background with white.
Try this: Choose PNG or a supported WebP/AVIF output if transparency is needed. Converting a white-backed JPG to PNG does not recreate transparency that has already been lost.
- The output format cannot be encoded in this browser
Some operations need browser codec support or additional codec modules. A file-type choice is not proof that the current environment can complete every encode.
Try this: Try JPG or PNG, or retry in another supported browser. Do not rename a failed or unsupported output to the desired extension.
- The result is withheld by the metadata check
The output scan recognized metadata that should not be present in the rebuilt image, so no download is offered.
Try this: Try another supported output format and report the input/output types if the problem persists. Do not treat a blocked export as a completed conversion.
- The image exceeds the working-memory budget
Decoded pixels and compatibility encoders need more memory than the compressed file size suggests. The limit is a conservative estimate, not a measurement of free device RAM.
Try this: If encoding is over budget, choose 1920 or 1280 under Output size and convert again, or try JPG/PNG. If opening the original is over budget, choose a smaller source image. Lowering quality alone does not reduce pixel dimensions.
Limits and compatibility
- Format and quality
- HEIC/HEIF are input formats only. PNG disables the quality slider because its encoding is lossless; a 100% setting on a lossy format does not promise a byte-identical result.
- One image at a time
- Processing happens locally within device memory limits. This is a still-image workflow; do not assume animation frames, multi-image containers, camera metadata or original colour profiles are preserved.
Your files and form values are processed on this device. Downloaded copies remain wherever you save them. See how to check local processing and our privacy policy for site data and optional services.
Common questions
- Does PNG preserve everything in the original file?
- No. It preserves the decoded pixels through lossless PNG encoding. Source compression, metadata, colour representation and container features are separate from those pixels.
- Can I set a width, height or maximum KB here?
- Output size can keep original dimensions or fit a copy within a 1920/1280-pixel longest edge. Use Image resizer for custom dimensions and Image compressor for a size ceiling, then inspect the final file after all steps.
Continue your document workflow
Maintained by Shakti Prasad Ram. Found a mismatch? Report the tool, browser and steps without sending a sensitive document. Back to the tool