Image tools

Edit images in your browser — fast, private, and free

Images are the heaviest thing most of us ship to the web, attach to an email, or hand off to a printer — and they are also the part of a project most likely to be done with the wrong tool. You do not need a sprawling photo-editing suite to crop a profile picture, you do not need a paid subscription to shrink a 6 MB phone photo down to something an email server will accept, and you certainly should not have to upload a private screenshot to an anonymous website just to convert it from PNG to JPG. The image utilities in this category exist to close that gap. Each one does a single, well-defined job — resize, compress, convert, crop, rotate, extract colors, strip metadata — and does it entirely inside the browser tab you already have open.

Because every tool here runs on your own device, the photo you load never travels across the internet. There is no upload progress bar because there is nothing to upload: the file is read locally, processed by the browser's canvas and image APIs, and handed back to you as a download. That single architectural decision changes everything about how the tools feel to use. They are instant, they work offline once the page has loaded, and they keep sensitive material — ID scans, contracts, medical images, unreleased product shots — on the only machine that should ever see them.

What you can actually do here

The category is built around the handful of operations that come up constantly in real work. Resizing is the most common: matching a header image to a 1200-pixel content width, fitting an avatar into a square, or hitting the exact dimensions a job application or government portal demands. Compression is the second: modern cameras produce files far larger than any web page needs, and a good compressor can cut a photo to a fifth of its size with no difference a human eye can detect at screen resolution.

Format conversion solves compatibility headaches — turning a HEIC photo from an iPhone into a universally-accepted JPG, swapping a PNG for a smaller WebP, or producing a transparent PNG from a flat image. Cropping and rotation handle framing and orientation, the two fixes almost every photo needs before it is presentable. And a set of smaller helpers round things out: pulling the dominant color palette out of an image, reading the EXIF metadata a camera silently embeds, or generating a favicon from a single source picture.

Typical jobs people bring to this category include:

• Shrinking a phone photo so it fits under an email or upload size limit without becoming a blurry mess.
• Resizing an avatar or banner to the exact pixel dimensions a social platform or CMS requires.
• Converting between PNG, JPG, WebP and other formats when a tool or website only accepts one of them.
• Cropping out a distracting background or trimming a screenshot down to the part that matters.
• Pulling a brand color palette out of a logo or reference photo for a design system.
• Stripping location and device metadata from a picture before sharing it publicly.

Why in-browser editing beats uploading to a server

The conventional online image tool works by uploading your file to a remote server, processing it there, and sending the result back. That model has three quiet costs. The first is privacy: once a file leaves your machine you have no real way to know how long it is retained, who can see it, or whether it ends up in a training set or a leaked bucket. The second is speed: a round trip across the network is always slower than a local operation, and it gets dramatically slower for large files or slow connections. The third is reliability: server tools go down, hit rate limits, or wrap the output in a watermark and a paywall right when you need it.

Doing the work locally removes all three. Your computer's processor is already fast enough to resize or compress an image in a fraction of a second, and it never charges you per use. The practical upshot is that you can run these tools on confidential material without a second thought, batch through dozens of files without waiting on a queue, and keep working even when your connection drops, because the page is just static code running in your tab.

Understanding image quality and file size

A surprising amount of frustration with images comes from not knowing the difference between dimensions, file size, and compression — three things that sound related but behave independently. Dimensions are the width and height in pixels and decide how large the image appears. File size is how many bytes the file occupies and decides how fast it loads and whether it fits within an upload limit. Compression is the trade you make between the two: it shrinks the file by discarding data, with 'lossless' formats keeping every pixel exact and 'lossy' formats throwing away detail the eye is least likely to miss.

For most web use, JPG and WebP at a quality setting around 75–85% give the best balance — files small enough to load quickly, with artifacts invisible at normal viewing size. PNG is the right choice when you need crisp text, sharp lines, or transparency, but it is wasteful for photographs. When you resize down, you also shrink the file; when you resize up, you do not add real detail, you only stretch what is there, which is why enlarging a small image rarely looks good. Keeping these three concepts straight makes it obvious which tool to reach for and what setting to choose.

Tips for getting the best results

Always start from the highest-quality original you have, because every edit and re-save of a lossy format loses a little more detail — you cannot recover what an earlier compression pass discarded. Resize before you compress so the compressor works on the final dimensions. If a file must stay under a hard limit, nudge the quality down in small steps and check the preview rather than guessing. And when transparency or sharp edges matter, stay in PNG; when smooth photographic gradients dominate, JPG or WebP will almost always win on size.

Resizing for the web versus for print

One distinction trips people up more than any other: the size an image needs depends entirely on where it will be seen. Screens think in pixels and care about dimensions, while print thinks in physical inches and cares about pixel density. An image that looks crisp filling a phone screen can come out blurry on paper, and a print-resolution photo is wildly oversized for a web page — wasting bandwidth and slowing the page for no visible benefit.

For the web, the rule is to match the pixel dimensions to the space the image will occupy and stop there. A blog header shown at 1200 pixels wide needs an image about that wide, perhaps doubled for high-density displays, and no more. Anything larger just gets scaled down by the browser, so you pay the file-size cost without gaining sharpness. Compressing that correctly-sized image then keeps the page fast.

For print, the math flips. Printers reproduce roughly 300 dots per inch, so a photo meant to print at four inches wide needs about 1200 pixels across to look sharp on paper. Resize below that and the print looks soft; the screen-perfect version is often not enough. Knowing which target you are aiming at — and resizing to its terms — is what separates an image that looks right from one that disappoints in exactly the medium that mattered.

Frequently asked questions