Images account for 42% of average page weight on the web (HTTP Archive, 2024). Unoptimized assets are the single biggest drag on Largest Contentful Paint (LCP) — a Core Web Vital that directly affects Google rankings. SizeMyPic gives you batch compression, resizing, and format conversion without leaving your browser or installing anything.
Drop images here or click to browse
Supports JPEG, PNG, WebP, and SVG
Google recommends keeping total page weight under 1.5MB for mobile. With images averaging 900KB+ per page (HTTP Archive), compressing and converting to WebP can cut image payload by 50-70%. SizeMyPic's quality slider lets you find the exact threshold where file size drops without visible degradation.
Serving a 2400px hero image to a 375px phone screen wastes bandwidth. Use SizeMyPic to batch-resize images into the breakpoints you need — 400, 800, 1200, 1600px — then use srcset to let the browser pick the right one. Aspect ratio lock prevents distortion.
WebP produces files 25-34% smaller than JPEG and 26% smaller than PNG at equivalent quality (Google). Browser support is at 97%+ (CanIUse). Drop your entire assets folder into SizeMyPic, convert to WebP, and download a ZIP. No CLI tools, no build step configuration.
SizeMyPic runs entirely in the browser using the Canvas API. No npm packages to audit, no ImageMagick to install, no Sharp to compile. Open the page, drop your files, done.
Your images never leave your device. There is no server upload, no temporary cloud storage, no data retention policy to worry about. Process client screenshots, internal assets, or pre-launch designs without any privacy risk.
Process dozens of images, then download them all as a single ZIP file. File names are preserved with the new extension, so you can drop the output straight into your project's asset directory.
Build-step tools are better for automated pipelines (CI/CD, static site generators). SizeMyPic fills a different gap — quick, manual batch processing when you need to optimize a set of images right now without configuring anything. It's useful for one-off tasks, prototyping, and projects where adding image processing to the build isn't worth the complexity.
Input: JPEG, PNG, WebP, and SVG. Output: JPEG, PNG, WebP (raster via Canvas API) and SVG (vectorization via ImageTracer). You can convert between any combination of these formats.
No server-imposed limits. Processing happens in your browser, so the practical limit depends on your device's RAM. Modern browsers handle batches of 50-100 images without issues. For very large batches (500+), process in groups to avoid memory pressure.