Clear, hands-on guidance for reducing image, video, and PDF file size in your browser.
When dimensions must stay nearly fixed, prioritize metadata removal, format choice, and gentle quality changes. Keep the master and verify the output instead of forcing an arbitrary file size.
Exact file-size targets are constraints, not quality settings. Learn how to reach 100KB, 500KB, 1MB, or 2MB with the least visible damage and how to verify the final bytes.
Quality 90 is not automatically better for the web. Export both settings from the same source, measure the bytes, and inspect the details that matter at 100% and at the real display size.
A browser interface does not automatically mean local processing. Check network requests, keep the original, resize and encode from a clean copy, and verify the downloaded JPG before sharing it.
Transparent PNGs can be smaller without losing alpha, but color reduction and matte mistakes can damage soft edges. Preserve the master and test the output on light and dark backgrounds.
There is no universal quality number for web images. Start with the display dimensions, select a suitable format, test a moderate visual target, and measure the delivered candidate in context.
Image compression can help Core Web Vitals, but only when the image is the bottleneck. LCP also depends on discovery and priority, while CLS depends on reserved space. Measure the full path.
Screenshots are not photographs. Protect text and one-pixel edges by cropping first, keeping enough pixels for the reader, testing PNG/WebP, and judging the final image at 100% and in context.