TinyPNG plugin review and common issues

Register for a free Tinify account at tinypng.com/developers. After registering, your API key is shown in the Tinify developer dashboard. In WordPress, go to Settings → TinyPNG – JPEG, PNG & WebP image compression and paste the API key. The key is sensitive — ensure no trailing spaces or line breaks. Free accounts get 500 compressions/month. If the key still shows invalid, verify your Tinify account email has been confirmed.

The 500 free compressions reset at the start of each calendar month. If you have hit the limit, new uploads will not be compressed until the reset (or until you add payment info to continue beyond the free tier). Tinify charges $0.009 per compression above 500 with no minimum payment. Add a credit card to your Tinify account to enable automatic processing beyond the free quota — usage is billed monthly. For large bulk optimization jobs, time them near your monthly reset to maximize free usage.

Unlike ShortPixel or Imagify, TinyPNG’s WordPress plugin does not automatically back up original images before compression. Once compressed, the optimized version replaces the original in the media library without a stored backup. To recover originals: restore from a full site backup created before optimization (UpdraftPlus, Duplicator, etc.). Going forward, enable WordPress’s built-in media backup or a site backup plugin before running bulk optimization with any tool that does not keep originals.

In Settings → TinyPNG, the plugin lists all registered WordPress image sizes with checkboxes. Deselect any thumbnail sizes you want to exclude from compression — for example, exclude “full” to keep originals uncompressed while compressing all thumbnails, or exclude a custom size that is used for a purpose where compression would be inappropriate. This also reduces API credit consumption per upload.

Yes — WebP conversion is available in TinyPNG’s plugin settings. Enable “Convert and store WebP versions” to generate WebP files alongside originals. Each WebP conversion counts as an additional API compression credit per image size. To serve WebP to supporting browsers, add server-side rules (.htaccess for Apache) or configure your CDN to prefer WebP. The plugin generates the files but does not handle browser-level format negotiation automatically.

For a small blog with fewer than 50 new images per month, TinyPNG’s free 500 compressions/month is sufficient without payment. ShortPixel’s free tier gives 100 credits/month — less generous. TinyPNG wins on free quota volume. For larger sites or those needing AVIF, custom folder optimization, or lossless mode options, ShortPixel is more feature-complete.

TinyPNG works on WooCommerce product images and produces good compression results. The limitation is credit consumption: WooCommerce generates many thumbnail sizes per product, so a store with hundreds of products can exhaust the free tier quickly. The pay-as-you-go pricing at $0.009/compression is transparent but can add up. For large WooCommerce stores, ShortPixel’s bulk credit packages (10,000 credits for $9.99) are more economical than TinyPNG’s per-compression pricing at scale.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.