Open the source before converting
Select the WebP in the viewer above and check whether it displays, including transparent edges and a full animation cycle when present. The viewer inspects files; it has no JPG export button. If it fails, record the message and compare a known-valid local WebP. A failed website download and a missing desktop decoder need different fixes.
Choose a JPEG result
For a browser task, convert WebP to JPG. Select the local file, let processing begin automatically and inspect the downloaded copy. An animated source becomes its first frame, and transparent pixels require an opaque background.
Decode to PNG when alpha matters
For a static output that keeps transparent pixels, use WebP to PNG. The browser route uses the first frame of an animated source. Check both the edges and the output dimensions before using it elsewhere.
Create WebP from PNG or JPG
The cwebp reference covers static PNG/JPEG input and WebP encoding. These examples show an explicit lossless PNG path and a lossy photo path; animated PNG and animated WebP are outside cwebp’s supported inputs.
cwebp -lossless input.png -o output.webp
cwebp -q 80 input.jpg -o photo.webpThe browser alternatives are PNG to WebP and JPG to WebP. An encoder’s quality option is not a universal measure that transfers unchanged between tools.
Match the command to your distribution
Package names and builds depend on the distribution release. Ubuntu 24.04’s webp package file list includes cwebp and dwebp, while Arch’s libwebp package entry identifies libwebp-utils for command-line tools. Check the package supplied for your own system rather than copying a version-specific installation command blindly.
If a command is missing, verify installation and executable lookup. If reading a file fails, check the actual format and decoder support; installing a desktop viewer does not necessarily add a command-line encoder.
Commands for a “convert WebP to JPG Linux” task
Record the installed versions and check ImageMagick’s listed WEBP read support and JPEG write support. Use quoted input paths and a separate output file. The browser PNG route can use an animation’s first frame, while dwebp rejects animated input rather than selecting a frame.
For local command-line work, ImageMagick 7 uses the magick command. A build with WebP reading support can produce a first-frame JPEG with an explicit white background:
magick -version
magick -list format
magick "input.webp[0]" -background white -alpha remove -alpha off "output.jpg"The quoted frame selector follows ImageMagick’s image-sequence options; alpha removal composites over the background. Keep the source and use a separate output filename.
Google’s dwebp utility writes PNG and related pixel formats, not JPEG, and does not support animated WebP. Use it for a supported static source:
dwebp -version
dwebp input.webp -o output.pngAfter each command, inspect its exit status and error output, then reopen the new file. Confirm its actual format, dimensions and background or alpha. A filename that exists is not sufficient proof that this run produced a valid result.
Keep animation separate from still conversion
For a GIF destination, use WebP to GIF and inspect palette and timing changes. For a supported video output, see WebP to MP4; codec availability depends on the build and the route does not add an editing timeline or audio to the source.
For GIF, an animated source supplies the frame sequence; a static input stays static. A still source remains a still view in a video container; it does not gain motion. For animated sources, verify frame order, pacing, loop behavior and the complete playback in the destination. The page does not expose trimming, frame-rate or duration controls.
Questions and answers
Practical answers for this task.
No. Its documented output formats include PNG and PPM-family formats, not JPEG. Use an appropriate JPEG-capable tool for that step.
The ImageMagick JPEG command explicitly chooses frame zero. dwebp is for supported static input, and the cwebp examples are static encoding tasks.
No. Desktop applications and command-line programs may use different libraries or builds. Check the specific tool’s capabilities.
No particular desktop app is required for the browser route. A local command-line workflow needs its own installed executable and codecs. Choose the route that fits your task, then verify the result in the application that will receive it.