Prepare images for a faster website
Turn photos and page graphics into WebP, at a width your layout actually uses. This is the usual path when a homepage feels heavy and the images are still full camera resolution.
Fast · 100% private · Always free · Any browser
Drop images anywhere on this page
JPG, PNG, WebP, GIF, SVG, or HEIC. Your photos stay on this device.
When to use this
WebP is the default here because it usually beats JPG on photos and can keep transparency for UI. Modern browsers all display it.
Stay on JPG if a CMS, email newsletter, or partner still rejects WebP. Stay on PNG for a logo that must stay exactly as drawn.
If page speed is the concern, shrinking width matters as much as the format. A 4000px WebP is still a lot of bytes.
How to do it
- Drop the images you plan to put on a page.
- Leave output on WebP and quality near 0.8 unless you see banding.
- Keep max width around 1600, or 2400 if the image displays at 1200 CSS pixels on retina.
- Download the WebP files and replace the originals in your theme or CDN.
Tips
- Hero photos: one large WebP, not a PNG screenshot of the photo.
- Product grids: consistent width helps caching and layout.
- If a client cannot open the preview, convert a copy to JPG. Keep WebP on the site.
Related
FAQ
- Do I still need a JPG fallback?
- Almost never for public websites in 2026. Keep a JPG if you support very old in-app browsers you cannot test.
- Will WebP break my WordPress media library?
- Current WordPress versions accept WebP. If an old plugin rejects it, convert that one asset back to JPG.
- Is this processed on your CDN?
- No. Encoding happens in your browser. We never see the files.