A “convert to WebP” or “compress to 200 KB” button looks like a server-side transcoder. In a Canvas-based browser tool, it is closer to decode, paint, and re-encode. The browser must be able to read the input. The browser must also be able to produce the requested output MIME type. Anything the decode-and-paint step does not preserve — animation, some color handling, original metadata — will not be in the download, even if the new file extension looks right. A quality slider of 100 is still a quality value passed to an encoder. It is not, in this design, a lossless mode switch.
ImagePixelConverter is a free, no-account set of in-browser tools for inspecting pixels and density, then resizing, compressing, and converting images. The site calls this a browser-local image lab and states that image bytes are processed on the device, without being uploaded to its servers. Transfers between tools in the same tab may keep a temporary copy in the browser for five minutes. Optional Google Analytics 4 runs only after Accept, according to the privacy policy dated 2 November 2026. External fonts and icon files are still requested from third-party hosts even when analytics is declined, and those requests can carry an IP address and ordinary browser details. The conversion and compression pages are clearest when you read them as Canvas export with documented limits, not as a guarantee of smaller files, better rankings, or bit-identical pixels.
Quality search, byte targets, and what the encoder will not do
ImagePixelConverter’s compress-image tool offers two modes. Leave the target field blank and the quality slider is used alone. Enter a target in kilobytes and the tool searches encoding quality first, then reduces pixel dimensions if the quality pass is still too large. One kilobyte means 1,000 bytes on this site, not 1,024. A target is not guaranteed: if the result remains above the cap, the status is marked clearly rather than dressed up as a success. After you change a setting, “Apply settings” is meant to reprocess the original files, which avoids repeatedly compressing an earlier output.
Format behavior in target mode is easy to miss. PNG and other non-lossy choices switch to WebP so that transparency can be kept; you have to choose JPEG explicitly if a form requires JPG, and JPEG then uses a white background. The tool writes JPEG, WebP, or AVIF when the browser can encode the selected format. Unsupported encoding produces an error instead of a silent fallback you might not notice. GIF, BMP, and ICO output are not provided by the native encoder this site uses. Animated inputs are exported as a still image; animation is not preserved. Export redraws the pixels, so original EXIF and other source metadata are not copied into the new file.
Several interface details affect how you should judge a result. The on-page thumbnail shows the source image, not a before-and-after comparison; the site tells you to download the output and inspect it at the intended display size. PNG quality is not controlled by the quality slider. Results depend on the image and on the browser’s encoder, so a number that worked on one photograph is not a portable quality setting. Smaller files do not guarantee search-ranking gains. For a form that states a 200 KB maximum, a companion preset page uses the same 1,000-byte kilobyte and still asks you to check dimensions and accepted formats before you submit.
The hard limits are numeric and memory-shaped. Exports allow up to 16,384 pixels per side and 80 million pixels in total; available device memory can impose lower practical limits. Inputs must be readable by the browser. There is no account and no daily conversion quota. A batch is a queue, one file at a time, with individual downloads or a ZIP of completed outputs. That envelope is not a quality claim.
JPG to WebP is a lossy re-encode, even at 100
The site’s JPG to WebP converter is one route in a larger format matrix. Each output option is checked by requesting a Canvas export and verifying its MIME type; unsupported choices are disabled. WebP and AVIF export depend on the browser. Auto, on pages that offer it, keeps the input format when it is encodable and otherwise uses PNG. For this specific pair, the source profile is lossy JPEG without transparency or animation, and the export is lossy WebP. WebP as a format can store animation and can be encoded losslessly; this tool exports a single still frame, and it has no separate lossless control. A quality setting of 100 does not guarantee lossless WebP output.
The page suggests 78–86 as a starting quality range for photographs. That is guidance printed on the tool, not a promise that text, hard edges, or fine patterns will survive. File size depends on the source image, the dimensions, and the browser encoder. The FAQ is direct: a smaller WebP file is not guaranteed, and you should compare actual output sizes. A smaller image can reduce transfer time and may help Largest Contentful Paint when that image is the page bottleneck; it does not guarantee a PageSpeed score or a search-ranking improvement. Measure the page after deployment if that is the reason you changed formats.
WebP supports transparency, but JPEG sources usually do not include alpha data, so this route will not invent a transparent background. Quality settings apply to lossy encoders; PNG and SVG wrapper exports ignore the slider. If the destination still requires JPEG, converting back is a second lossy step. Keep the original when exact source data matters. The conversion is useful for a still WebP at a compatible destination if you inspect the download. It is not a rule that WebP is always smaller, and the site’s comparison pages say the same: there is no fixed compression saving that applies to every image.
A PNG-to-SVG export can be a bitmap in a wrapper, not a vector trace
ImagePixelConverter’s PNG to SVG page is unusually plain about what it does not do. The page title describes a wrapper, not a vector trace. The target profile is a PNG bitmap in an SVG container. Transparency can be preserved on this route. Enlarging the result reveals pixels. The SVG wrapper adds file-size overhead, so the new file can be larger than the PNG you started with. The quality slider is ignored for PNG and SVG bitmap exports, because those paths are not using a lossy quality parameter in the way JPEG or WebP do.
That behavior matters in any workflow that treats “.svg” as scalable artwork. A true vector path can be redrawn at a new size without a pixel grid. A bitmap embedded in an SVG is still a raster image with an XML envelope. If a build step, a CMS, or a design tool assumes that any SVG is line art, this export will not meet that assumption. The related SVG-to-PNG route is the other direction: the browser renders what it can and writes a Canvas pixel buffer as PNG. In both directions, the tool exports still images. Animated inputs become a single frame. Original metadata is not copied. PNG encoding is lossless only for the rendered pixel buffer the Canvas supplies; browser decoding or color conversion can change source pixels, and source profiles or metadata may differ.
The same honesty shows up in the format matrix as a whole. Reading an input and exporting an output are separate browser capabilities. GIF, BMP, and ICO output are generally unavailable through Canvas in this implementation, even though those types appear as destinations in the matrix and are disabled when the encoder check fails. SVG output, whenever it is offered, embeds a bitmap rather than tracing vector paths. AVIF encoding is available only when the browser provides it. These are not marketing footnotes. They are the difference between a file that opens and a file that is the kind of file you thought you requested.
If you use these tools as a local pre-flight step, the useful habit is conservative. Compare the downloaded file with the original at the size it will actually be shown. Do not infer quality from the on-page thumbnail. Do not treat a reached byte target as proof that typography is still readable. Do not treat an SVG extension as evidence of vectors. And do not treat a local-processing statement as a complete privacy guarantee: image bytes are claimed to stay in the browser, while analytics, if accepted, and third-party font or icon requests, even if analytics is declined, are a different channel. Keep the original when you still need animation, metadata, or an un-reencoded source.
Top comments (0)