Resize JPG Online
Resize any JPG image to the exact pixels you need. The output is always a JPG, and transparent PNGs or WebPs you drop in are converted with a white background. Everything runs in your browser.
Upload an image
Drop an image here, or click to browse
JPG, PNG, WebP · Max 50 MB per file
Your image stays on your device. This tool runs entirely in your browser. Your file is never uploaded to our server.
How do you resize an image to JPG?
Resizing an image to JPG on this page is a four-step loop: drop the file, set the output size, check the preview, and download. The tool accepts JPG, PNG, and WebP files up to 50 MB, and it always writes the result as a JPG, so a transparent PNG dropped in comes out with its transparent areas filled white. Because the whole job runs in your browser with the Canvas API, nothing is uploaded, and the preview shows the exact output dimensions before you download.
- 1Drop or select an image. JPG, PNG, and WebP files up to 50 MB are accepted.
- 2Pick a mode: Pixels for an exact width and height, Percent to scale by a set amount, or Max dimension to cap the longest edge.
- 3Check the preview and the estimated size, then download. The output is always a JPG.
How much smaller will a resized JPG get?
Resizing cuts file size by removing pixels, and the savings scale with the drop in dimensions. A 4032x3024 camera photo at 3.8 MB resized to 1600px wide typically lands around 600-900 KB, because only about a quarter of the original pixels are left to encode. Halving the longest edge reduces the pixel count to roughly 25%, which is why resizing alone often beats a heavy compression pass. The preview shows the exact dimensions and estimated size before you download, so you can confirm the saving before committing.
Common use cases for resizing to JPG
Marketplace and store listings
Platforms such as eBay, Etsy, and Amazon re-sample oversized uploads and add their own compression on top, which can blur a listing photo. A 4032x3024 product shot uploaded at full size gets downscaled twice. Resized to 1600px on the longest edge first, the same shot uploads at roughly 700 KB instead of 3.8 MB and stays sharp in the feed.
CMS and blog hero images
A hero image saved at 5184px wide forces the browser to download and downscale a file far larger than any screen needs. Resized to 1920px wide, the file drops from around 6 MB to under 1 MB, and the page paints noticeably faster. JPG output also means the file works in any CMS that rejects WebP or PNG uploads.
Email attachments
Mail servers cap messages around 25 MB, and full-resolution phone photos hit that limit fast. Twelve 3 MB photos total 36 MB. Resized to 1200px on the longest edge, each drops to roughly 300-400 KB, and the whole set fits in a single message that opens instantly on a phone.
Social media posts
Most feeds downscale images to around 1080px or 1600px wide, so uploading a 3000px original wastes bandwidth for no visible gain. Resizing a 3000x2000 photo to 1600px wide cuts it from about 2.5 MB to under 800 KB, and the post looks identical on screen.
Three resize modes
- Pixels: set an exact width and height. Use this when a template or upload slot requires a fixed size, such as a 1200x630 social card.
- Percent: scale by a single number, so 50% halves both the width and the height.
- Max dimension: cap the longest edge at a value like 1600px, and the shorter side follows automatically.
Why is the aspect ratio lock on by default?
The lock keeps width and height linked, so changing one dimension scales the other in proportion. That prevents the squashed or stretched look that appears when the two are typed independently. Leave it on for every normal resize, and turn it off only when you deliberately need to distort the image to fit a non-standard slot.
What happens to transparency?
JPG cannot store an alpha channel, so any transparent area in a PNG or WebP source is filled with white in the output. A logo on a transparent background comes out on a white one, which is usually what a CMS or marketplace expects. If transparency needs to survive, use the PNG or WebP resizer instead; if the destination insists on JPG, this page produces exactly the file it will accept.
What quality setting should you use?
The quality slider controls how hard the JPG encoder compresses the result, and it shows only for JPG output. For most web images, 80% is the point where the file is light and the visible difference is hard to spot. Dropping below 60% starts to show blocking on edges and gradients, while 90-95% keeps near-original detail for a file you may zoom into.
- Avatars and thumbnails: 60-70%. Viewed small, so the eye tolerates more compression.
- Blog and content images: 75-85%. Detail holds up at normal screen sizes.
- Photos you might zoom into: 90-95%. Keeps texture intact at the cost of a larger file.
Why resize in the browser?
Every image on this page is processed locally by the Canvas API, so the file never leaves your device. There is no upload, no account, and no queue, which makes the tool a sensible choice for client assets, internal screenshots, and personal photos you would rather not send to a third-party service. Processing starts the moment the file is selected, and a single resize is typically ready in under a second.
Frequently asked questions
Are my images uploaded anywhere?
No. The resize runs entirely in your browser with the Canvas API, so the file never leaves your device. There is no upload step and no account.
What size should I resize a JPG to for the web?
A longest edge of 1600-1920px covers almost every use. Use 1920px for full-width hero images, 1200-1600px for body and blog images, and around 800px for thumbnails.
Does resizing a JPG reduce its quality?
Shrinking removes pixels without degrading the ones that remain, so visible detail holds up. The only loss comes from the JPG re-encode, and at 80-90% quality the result is effectively indistinguishable from the original.
Can I resize a PNG or WebP to JPG on this page?
Yes. Any JPG, PNG, or WebP up to 50 MB is accepted, and the output is always a JPG. Transparent areas in a PNG or WebP source are filled with white, because JPG cannot store transparency.
What happens if I enlarge an image past its original size?
Enlarging past the original adds blur, because the browser has to invent pixels that were never captured. For crisp results, resize to the original size or smaller.
Is there a file size limit?
Input files are limited to 50 MB. The cap exists because the tool decodes the full image into browser memory, and larger files make the page sluggish. Most photos are well below the limit.
Does resizing also compress the image?
Resizing and compression are separate steps. Resizing removes pixels, which alone usually cuts most of the weight. The quality slider then controls the JPG re-encode if you need the file even smaller.