Image Tools
Tools for working with images — converting between WebP, PNG and JPG, making favicons, compressing to a size in KB, resizing and turning images into a PDF, all in your browser.
Quick tasks
One click opens the tool already set up for the job.
Online Image Tools - Convert Between WebP, PNG and JPG
Picking an image format is one of those decisions that looks trivial and quietly determines how fast a page loads. A photograph saved as PNG can be five times the size of the same photograph as JPG with no visible benefit. A logo saved as JPG picks up grey smudges around every edge. This category is about getting an image into the right format for what you are doing with it, and about what the file reveals besides the picture.
What is in this category
| Tool | What it does | Reach for it when |
|---|---|---|
| Image Converter | Converts images to WebP, PNG, JPG, ICO or PDF, compresses them to a size in KB and resizes them, in bulk | A file is in the wrong format, too large for an upload limit, rejected by a form, or has to go out as one PDF |
| EXIF Viewer & Remover | Shows the hidden data in JPG, PNG and WebP photos, including the GPS position, and removes it without re-compressing | A photo is about to be posted, sold with or sent to someone, and should not reveal where or when it was taken |
| QR Code Reader | Reads a QR code from an image, a pasted screenshot or the camera, and shows links, Wi-Fi details and contacts | A QR code is on your own screen, in an email or a PDF, or you want to see a link before opening it |
Which format to choose
| Format | Compression | Transparency | Best for |
|---|---|---|---|
| JPG | Lossy | No | Photographs and any image with smooth gradients |
| PNG | Lossless | Yes | Logos, icons, screenshots, line art, anything with sharp edges or flat colour |
| WebP | Both | Yes | The web default - typically 25-35% smaller than JPG at the same quality |
| GIF | Lossless, 256 colours | Yes (1-bit) | Short animations; superseded by video and animated WebP for almost everything else |
The distinction that decides most cases is lossy versus lossless. Lossy compression discards information the eye is unlikely to notice, which works beautifully on a photograph and badly on a screenshot of text. Lossless compression keeps every pixel exactly, which is essential for a logo and wasteful for a landscape.
The second question is transparency. JPG has none. If an image needs to sit on a coloured background without a white box around it, the choice is PNG or WebP, and WebP is smaller.
Why WebP is usually the right answer for the web
WebP does both jobs: lossy compression that beats JPG at equivalent quality, and lossless compression with an alpha channel that beats PNG. In practice that means 25-35% smaller files for photographs and often 20% or more for graphics, with no visible difference. Every current browser supports it - Safari joined in 2020 - so the compatibility argument that used to hold people back has expired.
The case for keeping JPG or PNG is narrower than it was: an image that has to work in an old email client, a file heading into software that will not open WebP, or an asset someone will download and edit. For anything served on a page, WebP is the default worth starting from.
Understanding the quality setting
For lossy formats, quality is a number roughly between 1 and 100 that trades file size against fidelity. The relationship is not linear and the intuition most people have about it is wrong. Going from 100 to 85 typically removes half the file size and produces a difference almost nobody can see. Going from 85 to 70 saves much less and starts to show. Below about 60, edges develop visible blocking and halos.
Useful starting points: 80-85 for photographs on a web page, 90+ for images that will be examined closely or printed, and lossless for anything with text or sharp lines in it. If you are converting an image that was already saved lossily, remember that each generation compounds - re-encoding a JPG at 85 does not restore what the first pass discarded, it discards more.
Practical conversions people actually need
- A form rejects your file. An upload accepts JPG and PNG but not WebP, or the reverse. Convert and resubmit.
- The file is over the size limit. Converting a PNG photograph to JPG or WebP usually clears an upload cap in one step.
- A screenshot is enormous. Screenshots are often saved as PNG, which is correct for text, but converting to lossless WebP keeps the sharpness and cuts the size.
- A logo has a white box behind it. It was saved as JPG somewhere along the way. Converting back will not restore transparency - the information is gone - but it tells you to go find the original.
- You are preparing assets for a page. Convert to WebP, keep a JPG or PNG fallback only if you actually support browsers that need one.
- Several scans have to be sent as one file. Choose PDF as the output and every image becomes a page of one document; JPG to PDF starts with A4 pages.
What conversion cannot do
Converting a format never adds information back. A blurry 400-pixel image saved as PNG is a blurry 400-pixel image; the lossless format simply preserves the blur perfectly. Detail discarded by an earlier lossy save is gone permanently, and converting JPG to PNG produces a larger file containing exactly the same visible artefacts. When quality matters, go back to the original source rather than converting a converted copy.
Metadata is worth a thought too. Photographs from a phone or camera carry EXIF data that can include GPS coordinates, the device model and the exact time the picture was taken. Conversion typically drops it, which is usually what you want before publishing an image - but do not rely on that as a privacy measure without checking. The EXIF viewer shows exactly what a photo contains and removes it without re-encoding the image.
A note on how this tool works
Everything on LogicUtil runs in your browser, and the image converter is no exception: images are decoded and re-encoded by the image engine your browser already has, so no file is uploaded and nothing is stored. That makes it safe for ID scans and private photos. The one thing that depends on your browser is which formats it can write. Safari, for example, cannot create WebP files, and the converter says so rather than saving a mislabelled file.
Related categories
- Encoding tools - Base64-encode a small icon to embed it directly in CSS as a data URI and save a request.
- Generator tools - produce a QR code when you need a scannable image rather than a converted one.
- Developer tools - convert colours between HEX, RGB and HSL while you are working on the same design.