WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am developing a WordPress theme, and when reading the Codex article on Theme review, WP recommendeds against allowing custom favicons in a theme. Does anyone know the reason for this recommendation?

From the Codex:

Themes are recommended not to implement custom favicon functionality.
If implemented, favicon functionality is required to be opt-in, and disabled by default.
If implemented, favicon functionality is required to support user-defined favicon images

share|improve this question
up vote 2 down vote accepted

Probably because a thing like a favicon is not necessarily tied to the on-page design, but to the branding of a site in general.

In other words: it's not specifically part of the "display" of the site. If a theme does choose to implemented it, an ender user might not want it (opt-in only) or they may want to use their own favicon (user-defined) to fit with their branding.

share|improve this answer
And that awkward moment when you see that über theme's default favicon in your site... – brasofilo Dec 5 '12 at 15:58
Okay, that makes sense. I'm setting it up as opt-in and not including my theme's favicon, so it sounds like that should be okay. – chowwy Dec 5 '12 at 16:34
Also, when a user changes themes, they don't expect their favicon to go away. Favicon functionality should be in a plugin. – Otto Dec 5 '12 at 23:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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