Images

WebP to JPG: choose a background, quality and useful dimensions

·

To convert a still WebP image to JPG, choose the file, set the background for transparent pixels and adjust quality or maximum dimensions if needed. ToolMellow creates a new JPG on your device, with an individual download for each image and an optional ZIP for a batch.

Use JPG when the recipient requires it or when that format fits your workflow. The conversion re-encodes pixels: it can change detail, flatten transparency and increase file size. Start with the defaults, inspect the actual JPG, then adjust the settings around the result you need.

WebP to JPG

Each accepted still WebP is re-encoded as a new JPG

This converter accepts still WebP and always writes JPG. A WebP source may use lossy or lossless compression and may have transparent pixels. Those source properties do not turn the browser’s JPG export into a lossless conversion or give JPG an alpha channel.

Animated WebP is refused instead of silently discarding its animation. Export a separate still frame in your original application first. Renaming a PNG, JPG or animated file to .webp does not make it an accepted still WebP.

Each accepted still WebP is re-encoded as a new JPG
SourceConverter resultPractical decision
Lossy still WebPA newly encoded JPGCheck edges, text and fine detail after conversion.
Lossless or transparent still WebPA newly encoded JPG with transparency compositedChoose the background and inspect the result.
Animated WebPConversion is rejectedExport a supported still frame first.

Google: WebP RIFF container and image featuresJPEG committee: JPEG standards and coding modes

Follow a short workflow and check the downloaded image

The starting settings are quality 90, a white JPG background, maximum image side 0 and no manual rotation or flips. Maximum 0 keeps the decoded dimensions after any selected rotation.

Settings apply to the whole queue. Convert once to see the result, then change only what you need. Editing a setting clears the earlier results so you can distinguish the next conversion from the previous one.

  • Choose one to 20 still WebP images. Further selections append to the queue.
  • Check the source filenames and previews, then remove unwanted inputs.
  • Choose the background for transparent pixels and the JPG quality.
  • Set a maximum side only if smaller pixel dimensions are useful; choose any needed rotation or flips.
  • Select Convert to JPG and compare the resulting dimensions and actual file sizes.
  • Download the JPGs or the ZIP, then inspect the files in the receiving application.

The file contents determine whether an input is WebP

The file picker offers WebP files, but conversion checks their actual headers and dimensions. A different supported image format can receive a generic source preview and still be rejected here because this route requires WebP. Preview success is not proof of accepted conversion input.

If a source cannot be read, export a fresh still WebP from an application that opens it and try again. An extension change does not repair corrupt bytes, change formats or bypass the size and pixel guards. Source validation occurs before the requested downsize.

Choose the color that replaces transparency in the JPG

JPG has no alpha channel. The converter fills its canvas with your chosen JPG background, white by default, then draws the decoded image over it. Fully transparent pixels take that color; partially transparent pixels blend with it.

The background control does not remove an opaque background already painted into the image. For example, opaque blue pixels remain image content, while a half-transparent red edge blends with a selected green background. JPEG encoding can further alter the exact colors.

Choose the color that replaces transparency in the JPG
Original pixelsSelected backgroundJPG appearance
Fully transparentWhiteWhite pixels
Fully transparentGreenGreen pixels
Partially transparent redGreenAn opaque blend of red and green
Opaque image pixelsAny selected colorThe image content remains, subject to encoding changes

Google: WebP RIFF container and image featuresMDN: OffscreenCanvas.convertToBlob format and quality

Adjust quality while comparing bytes and visible detail

The quality slider ranges from 10 to 100 and starts at 90. It supplies the browser’s JPG encoder with a parameter from 0.1 to 1. Quality 100 is not a guarantee of lossless output, identical pixels, preserved source detail or a particular file size.

Compare useful features in the actual JPG: thin text, hard edges, gradients and small texture. A lower value may reduce bytes while increasing visible artifacts. A higher value cannot recover detail already missing from the WebP, and repeatedly saving JPG can add further changes.

MDN: OffscreenCanvas.convertToBlob format and qualityJPEG committee: JPEG standards and coding modes

Maximum image side preserves proportions without enlargement

Set Maximum image side to 0 to retain the decoded size after any selected quarter-turn. A positive whole number from 1 to 12000 bounds the longest output side. Smaller limits reduce both dimensions proportionally, with whole-pixel rounding; a larger limit does not enlarge a smaller image.

For example, 4032 × 3024 bounded to 1200 becomes 1200 × 900. A 90-degree turn changes the corresponding result to 900 × 1200. This route has no separate width/height box, crop selector or enlargement switch. Use a dedicated editing tool when those controls are needed.

Rotate first, then flip in the output image’s axes

The clockwise rotation choices are 0, 90, 180 and 270 degrees. Horizontal and vertical flips apply after the chosen rotation, in the axes of the resulting image. All queued files use the same global settings; this converter has no per-file rotation button.

WebP EXIF orientation is not guaranteed to be applied. Check the JPG’s orientation and correct it with the available clockwise turns or flips, then inspect the result again.

MDN: worker createImageBitmap orientation and color conversion

Source previews and output previews answer different questions

Source thumbnails show the decoded source in a preview bounded to 640 pixels on its longest side. They do not update to show your selected rotation, JPG background or quality. The expected-dimensions caption describes the planned geometry, rather than promising the final appearance.

After conversion, the result preview displays the encoded JPG, scaled to fit the page. It helps you spot an obvious mistake, but inspect the downloaded image at a useful zoom for fine detail, partially transparent edges and the recipient’s display or print workflow.

Queue order determines numbered downloads and ZIP entries

You can move files, sort by filename, reverse the queue or remove individual files. Filename sorting follows the selected language with numeric comparison, so names containing numbers can sort naturally. These actions invalidate earlier results while retaining the global image settings.

Results use order prefixes and sanitized JPG basenames, such as 01-photo.jpg. Two identical basenames still receive different prefixes. With multiple results, Download all as ZIP creates toolmellow-images.zip; it bundles the converted JPGs rather than merging them into one picture.

Check file bytes, pixel dimensions and batch totals separately

The input count, each file’s bytes, cumulative source bytes, source dimensions and cumulative encoded JPG bytes are separate limits. A small compressed WebP can still describe too many pixels. Asking for a tiny output does not bypass the source guards.

The values below use decimal bytes. The 100000000-byte encoded limit covers the JPG buffers together; ZIP wrapper overhead is separate. This route has no PDF-specific 50 MB result limit, no exact file-size target and no promise that every device can comfortably process a job near the bounds.

Check file bytes, pixel dimensions and batch totals separately
BoundMaximum allowedApplies to
Inputs20 filesOne conversion job
Individual source25000000 bytes (25 MB)Each selected WebP
Combined sources100000000 bytes (100 MB)All input files together
Source pixels24000000 pixels (24 MP)Each source image
Source side12000 pixelsEither side of each source image
Combined encoded output100000000 bytes (100 MB)All resulting JPG buffers together

A valid converted JPG can be larger than its WebP source

Changing format does not guarantee a smaller file. WebP and browser JPG encoding make different tradeoffs, and a small lossless WebP with simple colors can become a much larger JPG. The converter reports actual source/output bytes and the percentage difference.

Conversion always returns the requested JPG when it succeeds, even if its byte count increased. It does not use Compress Image’s exact-original fallback. Try a lower quality or smaller maximum side if the recipient needs fewer bytes, then check that the result remains useful.

Check metadata and color in the receiving workflow

This WebP-to-JPG path does not copy original EXIF into the output. The encoder can add its own metadata fields. This is not a general metadata/GPS sanitation workflow, and it does not guarantee that original color profiles or print appearance are preserved.

The browser decodes and re-encodes the image. Check orientation and color in the application that will use the JPG. If a workflow requires supported metadata retention or color-managed editing controls, choose a tool that explicitly provides those controls.

Google: WebP RIFF container and image featuresMDN: worker createImageBitmap orientation and color conversion

Recover from errors without confusing old and new results

A later bad image fails the conversion job instead of returning earlier partial results. Remove or replace the offending source, or correct an invalid global setting, then convert again. If adding files would exceed 20 inputs, that entire addition is refused and the existing queue stays in place.

Cancel terminates the conversion worker and keeps your original input list. The whole job, including worker startup, has a 60-second deadline. Clear files removes inputs/results and clears errors while retaining global quality, background, maximum-side, rotation and flip settings. ZIP creation is a separate browser-main-thread operation with no separate conversion Cancel control.

Local conversion and follow-on actions have a limited scope

Image processing runs on your device. The page and its worker/library resources can still load over the network, so local processing does not mean the site is an installed offline application. Closing or reloading the page can discard the current working state.

A result can be sent to the separate resize or PDF tool, and multiple results can be sent together to JPG to PDF. These are explicit, one-use handoffs held in memory in the same tab, not durable storage or a shareable URL. The receiving tool applies its own input limits and controls.

Choose the next tool around the actual task

Keep the original WebP while deciding which result fits the recipient. Choose a transparent output workflow when alpha matters, a resizing or editing workflow for geometric changes, and PDF only when you need document pages. A separate editor can supply a supported still frame or change an opaque background before conversion.

Choose the next tool around the actual task
NeedUseful workflowWhat to check
Keep transparencyWebP to PNGRendered alpha and actual output size
Set a pixel box or crop positionImage Resizer or an editorInput bounds, fit and final dimensions
Reduce an existing JPGCompress ImageActual size and visual quality
Place images into document pagesJPG to PDFPage layout and the downloaded PDF
Extract a still or change opaque image contentYour image editor, then a supported conversionA valid still source and the intended appearance

Adobe Express: image formats and export workflow

Common questions

How do I convert WebP to JPG?

Choose a still WebP, adjust quality/background and any maximum-side or rotation settings, then select Convert to JPG. Inspect the result and download it. Further file selections append to the queue; settings apply to all inputs.

Why does transparent WebP get a background in JPG?

JPG does not support an alpha channel. Fully transparent pixels take the selected background, white by default, and partially transparent pixels blend with it. The control does not remove an existing opaque background.

Does quality 100 make WebP to JPG lossless?

No lossless or identical-pixel result is promised. Quality 100 is the highest browser encoder parameter offered here, not 100% preserved detail. This converter re-encodes the decoded pixels as JPG, including when the WebP input uses lossless compression.

Can I convert an animated WebP file?

Animated WebP is rejected rather than silently losing its animation. Export a separate still frame using an application that supports the source, then provide a valid still WebP. Renaming the animated file does not remove the animation.

Why can a WebP smaller than 25 MB still be rejected?

File bytes are only one bound. Each source is also limited to 24000000 pixels and 12000 pixels on either side, the job to 20 files and 100000000 source bytes, and the format must be readable still WebP. A small requested output does not bypass those checks.

Does maximum image side 0 keep the original size?

It retains the decoded pixel dimensions after any selected rotation. A turn of 90 or 270 degrees swaps width and height. A positive maximum preserves proportions and never enlarges. WebP orientation metadata is not guaranteed to be honored, so inspect the actual result.

Will WebP metadata and orientation be preserved?

Original EXIF is not copied by this path, and a WebP orientation tag may be ignored by the browser decoder. Check orientation and use a manual turn when needed. Encoder-generated metadata may still exist; general metadata sanitation and color-profile preservation are not certified.

Why is my converted JPG larger than the WebP?

The formats and encoders differ, and JPG overhead or quality can outweigh the source’s compact representation. Successful conversion returns the JPG even when larger. Compare actual bytes and try lower quality or smaller dimensions if useful.

What happens if I cancel a batch conversion?

The conversion worker terminates and your input list remains. The job does not return earlier partial results if interrupted or failed. You can correct settings or inputs and retry. The whole conversion has a 60-second deadline, including startup.

Can I choose a separate rotation for each WebP?

This converter applies one rotation and its flip settings to the whole queue. Convert groups needing the same correction separately, or prepare individual images in an editor first. Moving files changes order without changing the global rotation.

Does the source thumbnail show my selected JPG background?

No. It is a smaller rendering of the decoded source and does not apply the JPG settings. Convert to see the encoded result preview, then inspect the downloaded file at a useful zoom.

Can I download the converted images together?

With multiple results, Download all as ZIP bundles the numbered JPG files into toolmellow-images.zip. Individual download remains available. If ZIP creation fails, download the results separately; ZIP creation runs in the browser’s main thread.

Are my images uploaded during conversion?

The conversion processes file contents on your device. Site, worker and library assets can still load from the network. Optional follow-on actions pass selected result files through temporary memory in the same tab; reloading can lose that handoff.

Does Clear files reset quality, background and rotation?

It removes the input queue and results and clears errors, while retaining the global image settings. Check those controls before adding the next batch. Changes to settings or queue contents clear earlier results so the next conversion produces a fresh result.

Primary references

Put it into practice.

Related guides