Tools
Fileraz
Tools
Fileraz
Try jpg to png, compress image, pdf…
Image tools
Most people arrive at a converter knowing the format they have and not the format they need, so: WebP is the right default for anything going on a website. It reaches comparable visible quality to JPEG in meaningfully fewer bytes, and unlike JPG it supports transparency, so a cut-out logo stays cut out. Browser support stopped being a concern some years ago.
PNG earns its place when you need lossless output or real transparency — screenshots, logos, line art, anything with sharp edges or text, and any image you intend to keep re-editing. The cost is size: a photograph as PNG is typically several times larger than the same image as JPG or WebP.
JPG is mostly a compatibility choice at this point. It is the format that every application, upload form, and print shop will accept, which is usually the actual reason to convert to it. Just remember it cannot hold transparency, so anything see-through in your source gets flattened to white.
Browser-side processing is not strictly better, and the last row is the honest cost of it. Here is the trade in full.
| Typical server-based tool | Fileraz | |
|---|---|---|
| Where your images are processed | Uploaded to the operator's servers | In your browser tab, on your own device |
| What the operator can see | The file contents, while processing and in any retention window | Nothing — the file is never transmitted |
| Usage limits | Commonly a daily cap or a size cap, with a paid tier above it | No cap, because your conversions cost us nothing to run |
| Account required | Often, for anything beyond the basics | Never — there is no public sign-up at all |
| Speed | Upload time, queue time, then download time | Starts immediately; bounded by your own hardware |
| Large or complex files | Handled well — server hardware does the heavy lifting | Bounded by your device memory, and may fail where a server would not |
Worth knowing before you start, rather than after.
Converters and the compressor take up to 30 images per batch; editors take one image at a time.
Format converters: quality slider for JPG and WebP; PNG is lossless.
JPG output flattens transparency — pick a background colour when converting from PNG, WebP, SVG, or ICO.
Phone photos use EXIF orientation when your browser supports createImageBitmap.
TIFF uses a bundled decoder — first page only on multi-page scans.
AVIF and ICO input depend on your browser decoder; failures mean try another browser or format.
Output is JPG, PNG, or WebP only — no AVIF, GIF, or ICO export.
No offline mode: there is no service worker, so the page must load over the network.
Compressor: PNG output is lossless — pick WebP/JPG output to shrink PNGs; slider applies to lossy formats only.
Resizer: aspect-ratio lock is on by default; enlarging warns because upscaling cannot add detail.
Cropper: export dimensions match the crop in source pixels, not screen density.
Rotate and flip: quarter turns or mirror only; JPG and WebP re-compress on export, PNG stays lossless.
Watermark: corner text overlay only — no logo upload, and not a DRM system.
Base64: PNG data URL about a third larger than the file; huge photos make huge strings.
EXIF stripper: re-encodes to drop most tags including GPS — it does not list fields and is not a forensic wipe guarantee.
Background remover, EXIF viewer, GIF maker: not available — no Convert UI; strip EXIF or convert stills with the live tools in the meantime.
Your browser decodes the image, draws it onto an HTML canvas, and re-encodes it in the target format using the Canvas API. Because every step runs in the page, the file is never transmitted. There is no WebAssembly involved in this path, despite what similar tools often claim.
Only when you convert it to JPG, which has no alpha channel and physically cannot store transparency. Transparent pixels are flattened to white before encoding. Convert to WebP instead if you need to keep the transparency.
WebP for anything going on a website, since it reaches comparable quality in fewer bytes and still supports transparency. PNG when you need lossless output or transparency preserved. JPG mainly when something downstream accepts nothing else.
None that we impose. Because the image is decoded into memory, the real ceiling is your device's available RAM, so a very large file can fail here where a server-based tool would cope.
No. The converters and editors handle one image at a time. For bulk work, command-line tools such as ImageMagick or cwebp are a better fit.
Decoding depends on your browser, and Chrome and Firefox cannot open TIFF this way. We have not bundled a dedicated TIFF decoder yet, so those pages do not currently work outside Safari.