Image Converter in the browser is not a generate
/free-tools/image-converter never spends a credit. Do not pay a model to do an in-browser file job.
/free-tools/image-converter never spends a credit. Do not pay a model to do an in-browser file job. PNG to JPEG is a Canvas encode, not a still a catalog row reinvented. Versely has no free generation tier — every model call bills credits, quoted before you confirm — so routing a format change through a generate is how you pay for a new picture you did not want.
The converter runs on the File API and Canvas in your browser. No upload. Disconnect the network and it keeps working. That is not a slogan about how carefully an upload is handled. There is no upload.
A format change is Canvas, not a model
A generate decides pixels. A converter re-wraps pixels you already have: PNG, JPEG, or WebP in, one of those three out. The quality slider does something on JPEG and WebP. PNG is lossless — the quality argument is ignored because there is no tradeoff to offer.
People send a logo to an image model "to make it a JPG." The model often returns a different logo: edges rebuilt, a mark legal no longer uses. Correct for a generate. A defect for a file job.
Use the converter when the pixels are right and a form, CMS, or printer wants a different container. Use a generate when the pixels are wrong.
PNG, JPEG, WebP — what actually happens
Pick the target for the constraint you actually have.
- WebP — usually smallest at the same visible quality; current browsers take it.
- JPEG — when something downstream refuses WebP. No alpha: this tool fills transparent pixels with white. An unhandled encode usually fills them black. If you needed the hole, do not convert to JPEG.
- PNG — transparency and flat art. Lossless. The slider will not shrink it.
The page reports input size and output blob size. It does not invent detail, upscale, or remove a background. Those are other tools, some of them generates.
Sibling file job: image compressor if you are staying in JPEG or WebP and only want quality. Do not send a PNG through a compressor and act surprised when lossless re-encoding does nothing.
When a credit is the right spend
Spend a credit when you need new information: detail that was never captured (upscale), a different object (image model), a moving still (image-to-video, billed per second).
Cost maps those formulas — per second, per 1,000 characters, per megapixel, per call. A format change is not on that map because it does not bill. Looking up a credit scenario to "export a JPEG" is the wrong surface.
No watermark, no account, no copy, no retention period. We never received the file.
Why this never bills
Generation costs credits because a model runs on our hardware. A Canvas encode runs on yours. A "free" converter on a generate endpoint would contradict the pricing page or spend margin on anonymous traffic. Utilities that never touch a model are free because they are free to run.
Do not prompt a video model to output a JPEG. Flatten alpha in the browser, on white, on purpose.
FAQ
Will converting in the browser reduce quality?
JPEG and WebP will, by the quality you set — that is the point of the slider. PNG will not; it is lossless. A generate can reduce quality and change the picture. The converter only does the first, and only on the formats that encode lossy.
Why did my transparent PNG become a white box as a JPEG?
JPEG has no alpha. The tool fills transparent pixels with white before encode so you do not get the black-box surprise of an unhandled conversion. If you need the transparency, export WebP or keep PNG.
Is this actually free, or does it use leftover credits?
It does not use credits. There is no account and no limit on the page. Generation on Versely is the opposite: no free tier, quoted in credits before you run it. This is not that meter.
When should I use a model instead of this converter?
When the still is wrong: you need different pixels, more pixels, or a new object. When the still is right and the file type is wrong, stay in the browser.