How to compress images for WordPress and CMS uploads

Most CMS platforms have upload size limits and compress images on the server anyway. Pre-compressing gives you control over the quality and ensures faster page loads.

CMS upload limits

Why pre-compress

1. Control over quality. CMS compression algorithms vary. Pre-compressing ensures consistent quality.
2. Faster uploads. Smaller files upload faster, especially on slow connections.
3. Better page speed. Serve optimized images immediately instead of waiting for server-side processing.
4. Storage savings. CMS storage is often limited or metered.

WordPress-specific tips

• Maximum upload size: Check Settings → Media for your host's limit.
• Thumbnail generation: WordPress creates 3 sizes by default (thumbnail, medium, large). Pre-compressing the original saves storage for all copies.
• WebP support: WordPress 5.8+ supports WebP natively. Use it instead of JPEG.
• Lazy loading: WordPress lazy loads images by default. Don't disable it.

Compression workflow

1. Resize first. WordPress displays images at max 1200px wide (theme-dependent). Don't upload 4000px images.
2. Compress to 80-85 quality. Visually identical, 60-70% smaller.
3. Use WebP if supported. 25-35% smaller than JPEG.
4. Upload and verify. Check the image looks good at display size.

Common mistakes

• Uploading raw camera photos. A 6000×4000 JPEG at quality 95 is 8-12 MB. Resize and compress first.
• Using BMP or TIFF. Convert to JPEG or WebP before uploading.
• Not compressing at all. Every 100 KB saved improves page load by ~0.1 seconds on 3G.

Recommended dimensions by WordPress context

WordPress serves the same image in many places, so size it for the largest spot it will appear, not for the original camera resolution:

Uploading a 4000px original for a 1200px slot forces every visitor to download data they never see. Resize to the display width first with Photo Resizer, then compress.

Plugin compression vs pre-upload compression

You can compress inside WordPress with a plugin (ShortPixel, Imagify, Smush) or before uploading. Each has trade-offs:

For most sites, pre-compressing with Image Compressor before upload gives the best quality-to-size result and avoids plugin credit limits. Use a plugin when migrating a large existing library.

Serving WebP in WordPress

WordPress has supported WebP uploads natively since version 5.8, so you can usually upload .webp files directly:

1. Upload WebP directly if your theme and host allow it — no plugin needed.
2. Or convert on the fly with a plugin that generates WebP and serves it to supporting browsers via the Accept header, falling back to JPEG for old ones.
3. Verify delivery in your browser's Network tab — the image Type should read webp.

WebP is 25-35% smaller than JPEG at the same quality, so switching format is often a bigger win than tuning the quality slider.

Frequently Asked Questions

Should I resize images before uploading to WordPress?

Yes. WordPress generates several scaled copies, but it starts from your original. Uploading a right-sized image saves storage across every generated copy and speeds up uploads.

Does WordPress compress images automatically?

It applies mild JPEG compression (around 82 quality by default) to generated sizes, but not to your original. Pre-compressing gives you consistent, predictable results.

Why are my images still slow after compressing?

Check that WordPress is serving the smaller generated size, not the full original, and that lazy loading is on. Image weight is only part of speed — see reducing image file size for web performance.

What quality setting is safe for WordPress photos?

Quality 80-85 (or WebP 78) is visually identical for most photos. For the reasoning behind those numbers, see compressing images without losing quality.

Related tools

• Image Compressor — compress before CMS upload
• Photo Resizer — resize to CMS-appropriate dimensions