Image Converter

Swap between JPG, PNG, WEBP, GIF, TIFF, ICO, CUR, and BMP with full metadata control and instant previews.

Back to Tools

Transcoding batch...

Drop images here or click to browse

Supports HEIC, AVIF, common RAW, ICO/CUR, ZIP bundles.

Process up to 50 files per batch ZIP archives unpack locally

Conversion queue

  • Queue files to preview status, estimated weight, and output names.

Conversion preferences

Advanced options

Prefer WEBP or PNG when you need alpha transparency. JPEG export auto-flattens to solid backgrounds.

Drop files to see live previews.

Batch progress

Files disappear from our servers right after we hand you the converted download links.

Converted files will land here with preview thumbnails, metadata, and download buttons.

<p>The <strong>JPEG converter</strong> turns any supported image into a JPEG file. JPEG (Joint Photographic Experts Group) is the most universally recognized image format on the planet: every operating system, every email client, every camera, every print shop, and every browser since 1992 reads JPEG without issue. The converter accepts PNG, WEBP, AVIF, HEIC, HEIF, BMP, TIFF, GIF, ICO, RAW files from Canon, Nikon, Sony, and other camera manufacturers, and produces a JPEG output ready for email attachments, print submission, archival storage, or any context where compatibility matters more than the smallest possible file size.</p> <h2>What "Converting to JPEG" Actually Does</h2> <p>JPEG is a lossy compression format. The converter decodes the source image into a raw pixel grid, then re-encodes the pixels using JPEG's discrete cosine transform: the image is split into 8x8 blocks, each block's color information is reduced according to a quality factor, and the result is written out as a JPEG file. By default the output runs at quality 95 with mid-range chroma subsampling, which is near-visually-lossless for photographs and produces files roughly 5 to 10 times smaller than the same image saved as a lossless PNG.</p> <p>Three things to be aware of when converting to JPEG:</p> <ul> <li><strong>Transparency is flattened.</strong> JPEG has no alpha channel. When the source has transparent regions (PNGs with transparency, HEIC with alpha, etc.), the transparent pixels are composited against a white background before encoding. To keep transparency intact, convert to PNG or WEBP instead.</li> <li><strong>EXIF metadata is preserved by default.</strong> Camera, lens, exposure, GPS, and capture-time tags carry through. There is an option to strip them before export, recommended before publishing photos online or sharing screenshots that may include location data.</li> <li><strong>Color profiles are kept.</strong> ICC color profiles are embedded in the output so colors look the same across screens that respect color management. This matters most for print preparation and brand-color work.</li> </ul> <h2>When JPEG Is the Right Output Format</h2> <p>JPEG is the right target whenever compatibility, ease of sharing, or print submission is the goal. Specific cases:</p> <ul> <li><strong>Email attachments:</strong> Gmail caps at 25 MB and Outlook at 20 MB. A handful of camera-original JPGs can blow through those limits, but converted JPEGs at default quality typically fit several photos within a single email.</li> <li><strong>Print shops:</strong> Most print services accept JPEG without question. The format preserves the embedded color profile, so what you see in your editor is what gets printed. For maximum quality submission, save at quality 100 or use TIFF instead.</li> <li><strong>Archival storage and backups:</strong> JPEG at high quality (90 to 95) is the standard format for long-term photo archives outside of professional RAW workflows. Universal readability over decades matters more than 10 percent extra compression.</li> <li><strong>HEIC from iPhones:</strong> iPhones save photos as HEIC by default to keep file sizes small, but most Windows tools, older Macs, and many web platforms cannot open HEIC without an extra plugin. Converting to JPEG is the standard first step before sharing or editing.</li> <li><strong>Submission to publishers, clients, or platforms with specific format requirements:</strong> Stock-photo agencies, news outlets, and print publications typically require JPEG. The format is the safe default when in doubt.</li> </ul> <h2>JPEG vs Modern Web Formats</h2> <p>JPEG is not the smallest format anymore. <a href="/en/image-converter/png-to-webp">Converting to WEBP</a> typically produces files 25 to 35 percent smaller than equivalent-quality JPEG, and AVIF goes smaller still. For modern web delivery where you control the server and browsers, WEBP or AVIF is the better choice. JPEG wins everywhere else: hostile environments (email, older browsers, dumb image viewers, print pipelines), where you cannot assume the receiver has modern format support.</p> <p>If your goal is to shrink an existing JPEG further rather than convert to it, use the <a href="/en/image-compressor">image compressor</a> with a lower quality setting. JPEG quality 80 to 85 is the sweet spot for web photographs: visually identical to quality 95 at normal viewing distance, with files 30 to 50 percent smaller. To pack a batch of JPEGs into a single document for print or archive, the <a href="/en/image-to-pdf">image-to-PDF converter</a> assembles them into a multi-page PDF with embedded color profiles.</p> <h2>Batch Conversion and Privacy</h2> <p>Each conversion runs in memory on the server. Source files stream to the processing endpoint, get decoded into a memory buffer, run through the JPEG encoder, and return as base64 inside the JSON response. Nothing is written to disk, indexed, logged, or cached. The buffer is cleared as soon as the response is sent. Up to 50 files per batch, 40 MB per file, with ZIP archives unpacked server-side and each entry counting against the same 50-file limit. Outputs are returned individually, or repackaged into a single download ZIP for batches above one file.</p> <h2 class="tools-section-title">FAQ</h2> <div class="collapse-group collapse-group-narrow"> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_1"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">What is the difference between JPEG and JPG?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>None. JPEG and JPG refer to the exact same format with the exact same encoding. JPG is just the short extension used in the early days of DOS and Windows, which limited filenames to three-character extensions. The Joint Photographic Experts Group standard was defined as JPEG, but the .jpg extension stuck. Files with either extension contain identical byte structures and are interchangeable.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_2"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">Will I lose quality when converting to JPEG?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>Some, yes, because JPEG is a lossy format. The converter runs at quality 95 by default, which is near-visually-lossless: at normal viewing distance the difference from the source is invisible. Going below quality 80 starts to show compression artifacts in skies, skin tones, and other smooth gradients. If you need a guaranteed pixel-exact copy, convert to PNG or TIFF instead. For most photographic content, quality 95 is the right balance.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_3"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">What happens to transparency when I convert PNG or HEIC to JPEG?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>JPEG has no alpha channel, so transparent pixels are composited against a white background during conversion. Logos, icons, and any image where transparency is part of the design will end up with a solid white backdrop in the JPEG output. If you need to preserve transparency, convert to PNG, WEBP, or AVIF instead. The choice depends on the destination: PNG for maximum compatibility, WEBP for smaller files where the destination supports it.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_4"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">Can I convert HEIC photos from my iPhone to JPEG?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>Yes. iPhones save photos as HEIC by default to keep file sizes small, but HEIC is not widely supported outside Apple's ecosystem. The converter accepts HEIC and HEIF as input and re-encodes them to JPEG. The original photo's EXIF metadata (capture date, camera model, exposure settings, GPS coordinates) is carried through. To strip GPS or other sensitive metadata before sharing, enable the metadata-removal option before converting.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_5"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">Should I use JPEG or WEBP for web images?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>WEBP if you control the destination and want smaller files, JPEG if you need universal compatibility. WEBP is typically 25 to 35 percent smaller than JPEG at the same visual quality and is now supported by every modern browser, so it is the safer default for the open web. JPEG is the right choice when the image will be processed by older tools, attached to email, sent to a print shop, or otherwise leave the controlled web environment. Many sites use JPEG as the fallback for browsers that do not support WEBP via the picture element.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_6"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">Why does my JPEG look worse after multiple saves?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>Because JPEG is lossy, every re-save discards some image data. The first save at quality 95 looks nearly identical to the source. Open that JPEG, edit it, save again at quality 95, and the second save discards more data from an already-compressed source. After several round-trips, compression artifacts (blocking, color smearing) accumulate visibly. This is called generation loss. Keep an original copy in PNG or TIFF if you plan to edit repeatedly, and only save to JPEG at the very end as the final delivery file.</p> </div> </div> </div> <div class="collapse-container collapse-faq" data-collapse-accordion data-collapse-group="seo-faq" data-collapse-no-save data-collapse-key="seo_faq_7"> <button class="collapse-header" type="button"> <div class="collapse-header-content"> <i class="fas fa-lightbulb collapse-header-icon" aria-hidden="true"></i> <span class="collapse-header-title">Are uploaded files stored anywhere?</span> </div> <i class="fas fa-chevron-down collapse-chevron" aria-hidden="true"></i> </button> <div class="collapse-content"> <div class="collapse-content-inner"> <p>No. Files are streamed to the conversion endpoint, decoded into a memory buffer, re-encoded as JPEG, and returned in the response. Nothing is written to disk, indexed, logged, or cached. The buffer is released as soon as the response is sent, so there is no copy left to recover. The tool requires no registration and does not track which images you have converted.</p> </div> </div> </div> </div>