WordPress, as you may know, comes with capabilities to upload media, which in particular means images and photos. What many users do not know is that WordPress generates up to three additional resized images for each image uploaded. This depends on the size of the image.

WordPress generates a thumbnail image with a resolution of 150×150, a medium sized image with a maximum resolution of 300×300 pixels and a large image with a maximum resolution of 1024×1024.

If the uploaded image is larger than 1024 in width or height, then all three image resolutions are generated. That’s a lot of additional storage space, considering that not all of those images are usually used in articles on the site.

If you have access to the server where WordPress is hosted, you can take a look at the wp-content/uploads/year/month directory to see that there are multiple resolutions available for each image that got uploaded in the past. Take a look at this screenshot for example.

If you look at the screenshot you notice that there are two and once even three copies of the original image on the server. In Ghack’s case, the 1024 resolution is not used at all, wasting a total of 438 Kilobytes in this example alone. And that’s only for one of the more than 9000 articles on this side. You can do the calculation but this seems like an awful lot of wasted storage space on the server.

So what can you do to reduce the number of copies that get generated during upload?

WordPress Image Generation

WordPress image generation is handled on the Settings > Media page in the WordPress admin interface.

If you visit the page you will notice three different image sizes that can be configured. These three image sizes are linked directly to the copies that get generated during media uploads.

Now for the tweak: Images will not be resized if you delete the size information in both the width and height fields. For example, if you only need a medium sized image with a maximum width and / or height of 500 then you can remove the resolutions from the thumbnail size and large size fields. If you do that, they will no longer be generated during media uploads. This reduces the number of files generated from a maximum of three to only one, which in turn means that a lot of space is saved on the server’s hard drive.

You need to assess your situation first before you make changes. Some WordPress themes make use of thumbnails and display them on the frontpage and individual pages of the blog. If that is the case the thumbnail generation needs to stay. It is usually still possible to remove either the medium or large size to reduce the storage space per uploaded image.

There have been some problematic messages occasionally when trying to publish posts lately. The error message Your attempt to edit this post [..] has failed appeared occasionally after upgrading to WordPress 2.7. WordPress was not able to publish the article which was bad enough but the underlying problem was that all work up to the point of the last auto save was lost as well.

This usually meant that the tags, categories and other last minute edits (like urls) were missing from the posts and had to be added again. The second edit and publishing always succeeded without difficulties.

The first thought was that this could have something to do with the automatic saves of posts before publishing. A quick research on the WordPress support forum seemed to confirm that.

The fix is apparently the following:

Locate the file post-new.php in the wp-admin folder of the WordPress installation. Find the following line in that file wp_enqueue_script('autosave'); and replace it with //wp_enqueue_script('autosave');.

The // in front of the row make the entire row a comment which essentially means that the command will not be executed. This will practically disable auto save during post publishing meaning that you will hacve to click on the Save Draft button before you leave an unfinished post page.