Image Format Converter

Conversion Receipt

{{ targetLabel }} {{ sourceInfo.width ? outputDimensionLabel : 'Sample ready' }} {{ sizingSummary }} {{ changeLabel }} {{ warnings.length }} note(s)

Source image:

Drop, paste, or browse one PNG, JPEG, WebP, GIF, SVG, AVIF, BMP, ICO, HEIC, HEIF, or other supported image.

Conversion settings continue below

Ignored {{ ignoredCount }} extra file(s). This tool processes one image at a time.

Output settings

Target format:

Choose the downloaded file format. Native and custom encoder support is checked in the results.

Image sizing:

Choose whether conversion should preserve source dimensions or resize during export.

Output width:

Enter the maximum or exact output width in pixels.

Output height:

Enter the maximum or exact output height in pixels.

Fit behavior:

Controls how the source image sits inside the exact output canvas.

Scale: {{ safeScalePercent }}%

Use values below 100 for downscaling; enable upscale before using values above 100.

Allow upscale:

Keep off for sharper production assets; turn on when an exact larger canvas must be filled.

Resampling quality:

High is best for final output; low can be faster for very large local images.

Quality: {{ safeQuality }}%

Use 80-92 for clean web output; AVIF support depends on the browser encoder.

{{ alphaTargetLabel }} alpha handling:

Preserve transparency, or flatten decoded alpha onto a solid background before export.

Flatten color:

Pick the color painted behind transparent source pixels before export.

Icon set:

Choose the square PNG payloads written into the ICO container.

Icon size:

Choose the single square icon payload size written into the ICO container.

{{ matteLabel }} background:

Pick the matte color used when converting transparent PNG, WebP, SVG, GIF, or HEIC pixels to {{ matteLabel }}.

Waiting for a browser-readable image.

Metric	Value	Detail	Copy
{{ row.label }}	{{ row.value }}	{{ row.detail }}

Check	Status	Detail	Copy
{{ row.label }}	{{ row.value }}	{{ row.detail }}

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Image format conversion changes how a picture is stored, delivered, and accepted by other software. The same visual image can become a compact WebP, a broadly compatible JPEG, a transparent PNG, a Windows icon file, or a large bitmap depending on the destination. The practical choice is usually about transparency, file size, browser or app support, and whether the next system needs a still raster image or a special-purpose container.

Conversion is not only a filename change. A browser or decoder reads the source image into pixels, then a new encoder writes those pixels into another format. That step can resize the picture, flatten transparent areas, discard camera metadata, and turn animated or multi-frame input into one still frame. A smaller output can be useful for delivery, but it can also hide quality loss or metadata removal that matters in production handoffs.

Good conversion work keeps the target use in view. A photo for a CMS often tolerates lossy compression; a logo with sharp edges or transparency usually needs PNG, WebP, AVIF, or an icon container; a legacy Windows handoff may need BMP or ICO even when the byte size is larger. The safest review compares the source dimensions, output dimensions, transparency result, warning notes, and final byte size before the converted file is used elsewhere.

Technical Details:

Raster conversion starts by decoding the source into a bitmap. Once the picture becomes pixels, the output encoder no longer has direct access to every original container feature. EXIF, GPS, embedded profiles, XMP blocks, HEIC sidecars, depth maps, and WebP metadata chunks may be lost because the new file is made from the decoded image, not copied as a container rewrite.

Browser encoders also differ by format support. PNG is the guaranteed fallback for canvas export, while JPEG, WebP, and AVIF depend on the browser's encoder support. BMP and ICO in this tool are assembled from decoded pixels, with BMP written as an uncompressed bitmap and ICO written as one or more PNG payloads inside an icon container.

Three-stage image conversion path from source image to decoded pixels to encoded output.

Transformation Core

The conversion path is source file to decoded pixels to optional resize or canvas fit to target encoder. Original dimensions keep the decoded width and height. Fit inside box scales the picture down or up to stay within the requested width and height. Exact canvas creates the requested output frame and then contains, covers, or stretches the source inside it. Scale percent multiplies both side lengths, with optional upscale control deciding whether values above 100 percent may enlarge the decoded pixels.

Image output format behavior
Target	Best fit	Transparency	Important limit
PNG	Sharp artwork, screenshots, and lossless handoffs	Preserved or flattened by choice	Quality setting is ignored because output is lossless
JPEG	Photos and broad app compatibility	Flattened to the selected matte color	Lossy compression can change fine detail
WebP	Compact web delivery with transparency support	Preserved or flattened by choice	Animated input exports as one still frame
AVIF	Very compact modern output when the browser encoder supports it	Preserved or flattened by choice	Unsupported browser encoders may return another type
BMP	Legacy Windows bitmap handoffs	Flattened to the selected matte color	Uncompressed output can be much larger
ICO	Favicons and Windows icon containers	Preserved or flattened by choice	Payloads are PNG-based icon images at selected square sizes

Input and output limits are there to protect the browser tab from memory-heavy files. Standard source images are capped at 40 MB, HEIC and HEIF sources at 80 MB, and output canvas area at 64 million pixels. Width and height controls clamp at 12,000 px, while scale percent runs from 1 to 400. These bounds do not judge visual quality; they only keep the local conversion work inside a manageable range.

Everyday Use & Decision Guide:

Start with the destination. Choose JPEG when a receiving system only accepts common photo files and transparency is not needed. Choose PNG when exact edges, screenshots, or transparent artwork matter. Choose WebP or AVIF when byte size is the main concern and the next browser or app can read the result. Choose ICO only when the handoff really needs an icon container, and choose BMP only for old workflows that ask for it directly.

Leave Image sizing at Original dimensions for a format-only change. Use Fit inside box for thumbnails or web images that must stay within a maximum frame. Use Exact canvas when a social preview, hero image, or icon source must land at a specific width and height. Contain keeps the whole image with padding, Cover crop fills the canvas by trimming edges, and Stretch fills the frame by changing the aspect ratio.

Keep Allow upscale off when sharpness matters; turn it on only when a larger exact canvas is more important than native pixel detail.
Use Quality between 80 and 92 for JPEG, WebP, or AVIF first passes, then compare the preview and byte-size chart.
For transparent source art, check Alpha handling before choosing JPEG or BMP, because those outputs need a solid background.
For ICO, use the favicon set for 16, 32, and 48 px, the app icon set for 32, 48, and 256 px, or the full set when the receiver may pick several icon sizes.

The main misread is treating a successful conversion as proof that every source feature survived. A converted preview can look right while metadata, color profile data, animation frames, HEIC sidecars, or WebP chunks were not retained. Check the Format Guidance rows and warnings before handing the file to another person or system.

Step-by-Step Guide:

Use the visible receipt and result tabs as checkpoints while moving from source image to final output.

Drop, paste, or browse one file in Source image. The drop area changes to Image ready, and extra files are reported as ignored.
Set Target format. If the source is HEIC or HEIF, the tool moves the target toward JPEG for the direct decoder path unless you later choose another target.
Pick Image sizing. For Fit inside box or Exact canvas, enter Output width and Output height. For Scale percent, move the Scale control and check the percentage shown beside it.
When Exact canvas is selected, choose Fit behavior. Contain pads, Cover crop trims edges, and Stretch changes proportions.
Set Allow upscale and Resampling quality when resizing is active. If the requested frame is larger and upscale is off, a warning explains that the image was not enlarged to fill the request.
Adjust Quality for JPEG, WebP, or AVIF. For alpha-capable targets, choose whether to preserve transparency or flatten it. For JPEG and BMP, choose the matte background color.
Open Converted Image and inspect the preview. Then check Conversion Metrics for Output dimensions, Transparency, Output file, and Size change.
If an error appears, reduce the file size or output dimensions, choose a browser-supported target, or retry after the HEIC/HEIF decoder has loaded.

When the warning badge is clear or understood, download the converted image or use the result tables, chart, and JSON for a handoff record.

Interpreting Results:

The Conversion Receipt gives the quick read: output byte size, target label, dimensions, resize summary, size-change badge, and warning count. A smaller result is useful only when the preview still looks acceptable and the destination can read the format. A larger result can still be correct for BMP, lossless PNG, or multi-size ICO output.

Conversion Metrics is the best audit table. Output dimensions confirms the final pixel frame. Transparency shows whether alpha was preserved or flattened. Size change compares the source and output bytes when both are available. For WebP and HEIC/HEIF sources, extra rows expose container or brand evidence before conversion.

Format Guidance is where false confidence usually gets caught. Browser encoder rows show whether PNG, JPEG, WebP, AVIF, BMP, and ICO are supported or risky in the current browser. Metadata, animated input, SVG rasterization, and special-format rows explain why a converted still image may not carry every source feature forward.

Use the Byte Size Comparison chart for quick before-and-after comparison, then use JSON when another workflow needs the selected target, sizing controls, source facts, output facts, support states, and warnings in one structured record.

Worked Examples:

Transparent PNG to WebP

A 960 x 540 PNG logo source is converted to WebP at 88 percent quality with Image sizing left at Original dimensions and Alpha handling set to Preserve transparency. Conversion Metrics should keep Output dimensions at 960 x 540, show Transparency as preserved where decoded, and show the target as WebP output. If Size change reports a smaller file and the preview keeps clean edges, the result is a good delivery candidate.

Camera HEIC to JPEG

A 4032 x 3024 phone photo with HEIC brands is loaded and converted to JPEG at 85 percent quality. The HEIF brands row helps confirm that the source was recognized before decoding. Transparency should become not supported or opaque, and Format Guidance should warn that HEIC metadata, depth maps, bursts, and sidecars are not intentionally preserved. The output may be larger than the HEIC source, so Size change should be reviewed before using the file as a storage-saving copy.

Square icon source to ICO

A 512 x 512 transparent PNG icon is converted to ICO with Icon set set to Full set and Alpha handling set to Preserve transparency. Conversion Metrics should add Icon payloads with 16, 32, 48, 64, 128, and 256 px. The warning about PNG payloads is expected. If an older receiver cannot read PNG-based ICO entries, export PNG separately or use a dedicated legacy icon workflow.

FAQ:

Does the image get uploaded?

No upload is made by the conversion flow. Local file inputs are decoded and re-encoded in the browser tab, while HEIC/HEIF support depends on the page's browser decoder being available.

Why did AVIF return another format?

AVIF output depends on the current browser encoder. If the browser cannot create the requested type, the warning list and Format Guidance rows call out the fallback risk.

Why did transparency disappear?

JPEG and BMP do not retain alpha in this workflow, so transparent pixels are flattened to the selected background color. Alpha-capable targets can also be flattened intentionally when Alpha handling is set that way.

Can it convert animated GIF or WebP files?

It can decode them as image sources, but the output is a single still frame. Format Guidance marks animated input as Still frame so animation loss is visible before export.

Why was my image rejected?

The browser path rejects very large sources and canvas outputs. Use a smaller source, reduce Output width and Output height, lower Scale percent, or disable a larger Exact canvas request.

Glossary:

Alpha: Transparency information in decoded pixels.
Canvas: The browser bitmap surface used for resizing, drawing, flattening, and re-encoding the image.
Matte: The solid background color painted behind transparent pixels when the target output cannot keep alpha.
HEIF brand: A short code in a HEIC or HEIF file header that identifies the container variant and compatibility profile.
ICO payload: One square icon image stored inside the ICO container.
Resampling: The pixel interpolation step used when an image is scaled to a new size.

References:

Image file type and format guide, MDN Web Docs.
HTMLCanvasElement: toBlob() method, MDN Web Docs.
High Efficiency Image File Format, HEIC/HEIX brands, Library of Congress.
ICO Format Overview, Microsoft Learn.
Icons, Microsoft Learn.