Article
Optimize website media for speed and Core Web Vitals
Images and videos typically account for 60 to 80 percent of a web page's total weight. Getting them right is the single highest-leverage thing you can do for loading speed, Core Web Vitals scores and search ranking. The good news: none of it requires specialized software or a server, and your files never need to leave your device.
Pick the right format before anything else
Format choice matters more than any quality slider. For photographs on a web page, WebP is the right default: it is 25 to 35 percent smaller than JPEG at the same visual quality and every modern browser supports it. AVIF compresses further still, up to 50 percent better than JPEG, at the cost of slower encoding. Use AVIF for hero images and product photos you compress once; use WebP for anything you process in batches or need quickly. PNG belongs only where you need lossless accuracy or a transparent background. SVG is the only sensible choice for logos, icons and illustrations: it scales to any size and often weighs a few kilobytes against hundreds for a rasterized equivalent.
Compress images without visible quality loss
Start by resizing to the actual display dimensions: a hero image that displays at 1280 pixels wide does not need 4000 pixels of data. Resize first, then compress. For photographs, quality 80 in WebP or JPEG is the practical floor below which casual viewers start to notice, so aim for 75 to 85 and look at the output at full zoom before publishing. For graphics with text and flat areas, PNG lossless or SVG preserves sharpness that lossy formats smear. The image compressor on this site handles all of these formats, runs entirely in your browser, and applies the same algorithms as dedicated desktop tools.
Convert video for the web without uploading it
Background loops and embedded video are where web media optimization often falls short. An MP4 with H.264 plays everywhere, but a WebM with VP9 is 20 to 40 percent smaller at the same quality, which matters for mobile users on constrained connections. The practical approach is to convert once to WebM, serve it as the preferred source in a video element, and keep the MP4 as fallback. The video converter here uses FFmpeg compiled to WebAssembly: the conversion runs inside your browser, nothing is uploaded, and files of any size work as long as your device has enough memory. For inline background video, also consider the video trimmer to cut out dead seconds before encoding: duration is the biggest driver of file size.
Inline assets: base64 and SVG
Very small images, icons and favicons embedded directly in HTML or CSS as base64 strings eliminate one network round-trip per asset. This makes sense for assets under about 2 KB that appear on every page, such as a logo sprite or a loading indicator. Larger assets should stay as separate files because base64 encodes 33 percent larger than the binary, and browsers cache file references but not inline data independently. The SVG optimizer removes editor cruft from exported SVGs without touching the visual output. The image-to-base64 converter generates the ready-to-paste data URI in your browser.
Tools in this article
- Compress images Reduce image file size without uploading. Quality slider or target file size in KB. Batch supported.
- Resize images Resize and convert your images (JPEG, PNG, WebP) without uploading them.
- SVG optimizer Optimize and minify SVG files with SVGO directly in your browser. No upload.
- Video converter Convert video between MP4, WebM, MKV and MOV (H.264/H.265/VP9) in your browser. No upload.
- Image to Base64 Convert images to Base64 data URIs (and back) directly in your browser. Copy, CSS snippet, no upload.
Frequently asked questions
Does image compression affect my search ranking?
Google uses Core Web Vitals as a ranking signal, and Largest Contentful Paint is almost always an image or a video poster. A page whose hero image loads in under a second scores better than one where it takes three seconds. Compression and the right format directly affect this metric, so yes, image optimization has a measurable SEO impact. The effect is strongest on mobile, where connections are slower and the penalty for heavy images is larger.
Why process media locally instead of using a web service?
Most online media tools require uploading your files to a remote server, which takes time, consumes bandwidth, and means a copy of your file exists on infrastructure you do not control. The tools on this site run entirely in your browser: your images and videos are processed on your device and the output is downloaded directly. There is no account, no upload wait, and nothing about your files is ever sent to a server.