BugWP logo BugWP
Back to Community
Home / Community / Plugin → Ewww image optimizer

Understanding and Managing EWWW Image Optimizer Database Tables

41 threads Sep 16, 2025 Plugin → Ewww image optimizer

Content

EWWW Image Optimizer is a powerful tool for improving website performance by compressing images. However, many users notice that after using the plugin, their database contains tables like wp_ewwwio_images that can grow quite large. This guide explains what these tables are for, why they remain, and how to manage them safely.

What Are the EWWW IO Database Tables For?

The primary table created by the plugin is wp_ewwwio_images. Its main purpose is to track which images on your site have already been optimized. This prevents the plugin from wasting server resources by re-optimizing the same images repeatedly. The table stores information such as the image path, original file size, optimized file size, and the optimization status.

Why Do the Tables Remain After Uninstalling the Plugin?

As seen in the sample threads, the EWWW Image Optimizer team deliberately designed the plugin to not automatically remove its database tables upon uninstallation. The reason for this is to preserve the optimization history. If a user deactivates the plugin temporarily or reinstalls it later, the plugin can pick up where it left off without attempting to re-optimize every single image again, which would be a significant drain on server resources.

Common User Concerns and Solutions

1. Large Database Table Size

Problem: The wp_ewwwio_images table can grow to several megabytes, especially on media-heavy sites, leading to concerns about database bloat.

Solution: If you are not using features like Scheduled Optimization and do not care if the plugin re-optimizes images in the future, you can safely empty this table. This can be done by running a TRUNCATE SQL command on the table (e.g., TRUNCATE TABLE wp_ewwwio_images;). This will remove all records and significantly reduce the table's size. Be aware that this will reset the plugin's memory, meaning a future bulk optimization would process all images again.

2. Cleaning Up After Uninstallation

Problem: You have uninstalled the plugin but want to remove all traces of it from your database and file system for a clean slate.

Solution: To perform a complete uninstall, you need to manually remove several elements:

  • Database Tables: Remove the wp_ewwwio_images and wp_ewwwio_queue tables.
  • Options: Delete any records in the wp_options table where the option_name begins with 'ewww_image_optimizer_' or 'wp_ewwwio_'.
  • WebP Images: If you used the WebP conversion feature, use the cleanup tool under Tools > EWWW Image Optimizer to remove the generated WebP files before uninstalling. Alternatively, you can manually delete them from your server.
  • Plugin Folder: Delete the /wp-content/ewww/ folder, which contains helper binaries. Note that newer versions of the plugin are designed to remove this folder on deactivation.

It is safe to remove all of these elements. Your original images, which are stored in the wp-content/uploads/ folder by WordPress, will not be affected.

3. Temporary Files and Debug Logs

Problem: You may find large debug.log files in the plugin's directory or old .bak files from image optimization.

Solution: The debug.log can be safely deleted. You can disable future debugging on the plugin's Support tab to prevent it from reappearing. The .bak files are backup copies of your original images created if you had the corresponding setting enabled. You can safely delete these via FTP or a file manager if you are sure you will not need the originals. To prevent them in the future, disable the "Save Originals" setting.

Important Considerations

  • Re-optimization: emptying or removing the wp_ewwwio_images table means the plugin will have no memory of previous optimizations. Any future bulk optimize operation will process all images from scratch.
  • Plugin Changes: The behavior described is based on historical plugin versions. The EWWW Image Optimizer team has made efforts to improve cleanup procedures in newer releases.

By understanding the role of these database tables, you can make informed decisions about managing your site's database size while maintaining the functionality of the EWWW Image Optimizer plugin.

Related Support Threads Support