That favicon wouldnt be cached already and you can make sure you new one is working.
Short of changing the name of the favicon, there is no way you can force your users to get a new copy This is a workaround for the chrome bug: change the rel attribute to stylesheet! Works like a charm: I came up with this workaround because we also have a requirement to be able to update customer's sites / production code and I didn't find any of the other solutions to work.
You don't have to clear your cache, restart your browser, or rewrite your HTML - you just need to change the icon's URL, once, so that the browser will forget the previously-cached icon.
Assuming that you've defined your icon via I recently restored my bookmarks and was looking for a way to restore the Fav Icons without visiting each page. For those in a similar circumstance merely download the FAVICON RELOADER addon.
I looked all around the web, and didn't find a good answer for testing favicons in local development.
In current version of chrome (on OSX) if you do the following you will get an instant favicon refresh: This way the Favicon will always refresh when it has been changed.
As pointed out in the comments you can also use the last modified date instead of the MD5-Hash to achieve the same thing and save a bit on server performance: Well, overhead is overhead, but yes, not too big.
Also, browsers are sometimes "greedy" about cached files.
This is especially helpful in production environments to make sure your users get the update.
This answer has not been given yet so I thought I'd post it.
If deleting the favicon from all your plugins temporary resolves the issue then you're very likely experiencing this: Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Your web browser will not go out to the internet to check for a new favicon on its own... If you put an "Expires: " header on the response, client browsers will re-request the icon after that timestamp.