The wordpress crop tool is greyed out for me in Firefox 3.6 (and IE7/8). I have disabled firefox add-ons and tried the solution here:

Wordpress Image Editor not working - conflict?

But this hasn't resolved the issue. Anyone know how wordpress determines whether to enable the crop button?

WP version is 3.0.1


  • 1
    Just realised that the button is disabled until you start dragging. The issue was caused by one of the installed plugins (I think). Just need to figure out which one now.
    – codecowboy
    Commented Oct 14, 2010 at 9:17
  • This is usually fixed by installing the "gd" library on the server. Your host needs to do something like yum install php-gd
    – Jay Brunet
    Commented Jun 12, 2018 at 22:19

4 Answers 4


For me, the button became available once I clicked and dragged the mouse cursor over part of the image to select an area to crop.

  • Wow, this is very unintuitive UI.
    – slhck
    Commented May 18, 2019 at 10:02
  • Yes, yes, a dramatic user interface. After setting the cropped area, I had to click the "Cropped" button again, after which the "Save" button was available. Look at @Mike Kormendy answer for step by step answer
    – kanlukasz
    Commented Nov 16, 2021 at 12:06

The crop tool and edit-image interface is not as intuitive as it could be.

For anyone looking for why the crop tool is deactivated and the save button is greyed-out, here are the steps for getting the crop tool to work:

  1. edit the image you wish to crop
  2. click the crop button above the image
  3. drag your area of the image you wish to crop the image to
  4. click the crop button AGAIN
  5. notice now that the image has been cropped, now hit the save button.

I'm 99% sure this was caused by the firephp plugin.

  • did deactivating the firephp plugin help you? can you link the firephp plugin?
    – hakre
    Commented Oct 14, 2010 at 18:29
  • yep. Link is inchoo.net/wordpress/wordpress-firephp-plugin
    – codecowboy
    Commented Oct 15, 2010 at 9:39
  • Then probably the WordPress FirePHP is not smart enough to know when it should shut up (in AJAX requests for example).
    – Jan Fabry
    Commented Oct 19, 2010 at 14:23

For anyone else where codecowboy's solution did not resolve the problem try this...

I had a very similar issue to what I think your experiencing over there... After hours and hours of trying to resolve it by coincidence I figured out that the problem was an extra space at the bottom of my custom functions.php file.

So... go and try this. Open your themes main folder and look for your functions.php file. Now go to the very bottom of the page and look for the closing ?> php tag. Now, make sure that there are NO tabs, spaces or line returns after the > including any comments or anything extra.

For me this fixed my issue and I think its a wordpress problem. If your still having the issue check to see if your calling any external php files within your functions.php file and if so do the same steps as listed above. Hope it helps someone.

  • 2
    This is not specific to WordPress, but to PHP. You cannot set HTTP headers if you already sent output. Having content outside PHP tags sends this output (as expected), and the crop functionality probably depends on Ajax with specific headers or content (not prefixed with empty lines). The solution is to leave off the closing PHP tag, this is still valid PHP, but prevents these kind of errors.
    – Jan Fabry
    Commented Oct 19, 2010 at 14:15
  • Very true... Still it's something I noticed so I figured I would share Commented Oct 21, 2010 at 5:41
  • 1
    Even better, avoid the closing PHP tag altogether. It's not required, and leaving it out can help to prevent this problem. More background: stackoverflow.com/questions/4410704/…
    – Tim Malone
    Commented Apr 5, 2016 at 6:47

Not the answer you're looking for? Browse other questions tagged or ask your own question.