{"id":4400,"date":"2011-02-23T03:38:03","date_gmt":"2011-02-23T11:38:03","guid":{"rendered":"http:\/\/www.oeconomist.com\/blogs\/daniel\/?page_id=4400"},"modified":"2020-05-19T06:01:32","modified_gmt":"2020-05-19T13:01:32","slug":"favicons-apple-touch-icons-and-site-thumbnail-images","status":"publish","type":"page","link":"https:\/\/www.oeconomist.com\/blogs\/daniel\/?page_id=4400","title":{"rendered":"FavIcons, Apple Touch Icons, and Site Thumbnail Images"},"content":{"rendered":"

This page is the first part of a discussion on supporting favicon<\/code>s, Apple Touch icons, and site thumbnail images<\/a>. First, I'll try to explain the rôles and invocations of these images without peculiar reference to WordPress<\/a> or to PHP<\/abbr><\/a>.<\/p>

If you're already quite familiar with these three sorts of graphics and with the HTML<\/abbr> to associate them with a webpage, and just want some PHP<\/abbr><\/a> which you can insert into a WordPress<\/a> theme to generate such HTML<\/abbr>, then you might want to go onto FavIcons, Apple Touch Icons, Site Thumbnail Images, and WordPress: The Code and How to Use It<\/q><\/a>.<\/p>

FavIcons<\/h4>

favicon<\/code>s are those images, typically tiny, associated with specific websites, in or beside URL<\/abbr> fields \"\" on browser tabs \"\" and especially in menus of bookmarks \"\"<\/p>

(The fav<\/code>[orite]icon<\/code> is named from Microsoft's practice of calling a browser bookmark a favorite<\/q>, begun as part of an effort to dominate use of the 'Net, in part by controlling the vernacular; and the favicon<\/code> was introduced as something first supported by MS<\/abbr>IE<\/abbr>.)<\/p>

Some browsers look for a favicon<\/code> as a file named favicon.ico<\/code><\/q> (and encoded in the Windows .ICO<\/code> format) in the basis directory or in the the highest directory of a domain. Some look for it as specified for a page by a tag of form<\/p>

<link rel="icon<\/u>" href="<\/code>imageURL<\/abbr><\/var>" type="image\/<\/code>mimeImageSubtype<\/var>" \/><\/code><\/blockquote>

such as<\/p>

<link rel="icon" href="http:\/\/www.oeconomist.com\/favicon.png" type="image\/png" \/><\/code><\/blockquote>

while others look for it as specified for a page by a tag of form<\/p>

<link rel="shortcut icon<\/u>" href="<\/code>imageURL<\/abbr><\/var>" type="image\/<\/code>mimeImageSubtype<\/var>" \/><\/code><\/blockquote>

such as<\/p>

<link rel="shortcut icon" href="http:\/\/www.oeconomist.com\/favicon.png" type="image\/png" \/><\/code><\/blockquote>

A reasonable response is to include both<\/em> tags in each webpage and, where possible, put a favicon.ico<\/code> in the highest directory of the domain. Putting a favicon.ico<\/code> in every remaining directory (even as a symbolic link to the image in the main directory) may not be worth the effort.<\/p>

Typically, a favicon<\/code> should be 16×16. The .ICO<\/code> format allows a website to deliver a set<\/em> of images in different resolutions, from which a browser might choose one most suitable to whatever it is doing, but such files are larger, and browsers won't necessarily make good use of alternate sizes.<\/p>

Apple Touch Icons<\/h4>

Apple Touch icons are graphics for the iPod, iPhone, iPad, and similar products to use in creäting virtual buttons linked to websites. \"\"<\/p>

In the absence of a specifying tag<\/em>, the highest directory of the domain is searched for a .PNG<\/code> with one of these names:

  1. apple-touch-icon-57x57-precomposed.png<\/code><\/li>
  2. apple-touch-icon-57x57.png<\/code><\/li>
  3. apple-touch-icon-precomposed.png<\/code><\/li>
  4. apple-touch-icon.png<\/code><\/li><\/ol> and the first if any found is used. (Adding -precomposed<\/code><\/q> to the name asks software not to tweak the image.)<\/p>

    Originally, the Apple Touch icon was to be 57×57. Now, for higher resolution iPods and iPhones, and for iPads, one is urged to also<\/em> supply 114×114 images (for higher resolution iPods and iPhones) and 72×72 images (for iPads). And, since this entry was first posted, there is a further standard size of 144×144; I am editting this series accordingly.<\/p>

    <\/p>

    The original tag for specifying an Apple Touch icon was of form<\/p>

    <link rel="apple-touch-icon" href="<\/code>imageURL<\/abbr><\/var>" \/><\/code><\/blockquote>

    or (again using -precomposed<\/code><\/q>)<\/p>

    <link rel="apple-touch-icon-precomposed" href="<\/code>imageURL<\/abbr><\/var>" \/><\/code><\/blockquote>

    typically<\/p>

    <link rel="apple-touch-icon" href="\/apple-touch-icon.png" \/><\/code><\/blockquote>

    In order to support icons of different resolutions, a sizes<\/code> attribute was introduced. its values are of form<\/p>

    width<\/var>x<\/code>height<\/var><\/blockquote>

    as in

    <link rel="apple-touch-icon" sizes="72x72" href="\/apple-touch-icon-72x72.png" \/><\/code><\/blockquote> <\/p>

    (In the absence of this attribute, an icon is presumed to have a 57×57 resolution.) Multiple resolutions are supported by multiple tags (with associated images).<\/p>

    Reasonable webdesign will employ a distinct image and distinct tag for each resolution supported by this class of devices,<\/p>

    <link rel="apple-touch-icon" href="apple-touch-icon-57x57.png" \/>
    <link rel="apple-touch-icon" sizes="72x72" href="apple-touch-icon-72x72.png" \/>
    <link rel="apple-touch-icon" sizes="114x114" href="apple-touch-icon-114x114.png" \/>
    <link rel="apple-touch-icon" sizes="144x144" href="apple-touch-icon-144x144.png" \/><\/code><\/blockquote>

    and perhaps for whatever seems to be coming down the pike. Given that one is using these tags, I don't think that there is a particular need to have a fall-back image in the highest-level directory.<\/p>

    Site Thumbnail Images<\/h4>

    Site thumbnail images are used when some other websites, such as Facebook<\/a>, link to the site with a thumbnail. \"\" In the absence of a specifying tag, some sites will try to find a suitable image, but may fail, or may choose one that the site owner would prefer not be used in such manner.<\/p>

    Some sites look for a tag of form<\/p>

    <link rel="image_src" href="<\/code>imageURL<\/abbr><\/var>" type="image\/<\/code>mimeImageSubtype<\/var>" \/><\/code><\/blockquote>

    such as<\/p>

    <link rel="image_src" href="http:\/\/www.oeconomist.com\/blogs\/daniel\/thumbnail_graphic.png" type="image\/png" \/><\/code><\/blockquote>

    Others look for a tag of form<\/p>

    <meta property="og:image" content="<\/code>imageURL<\/abbr><\/var>" \/><\/code><\/blockquote>

    such as<\/p>

    <meta property="og:image" content="http:\/\/www.oeconomist.com\/blogs\/daniel\/thumbnail_graphic.png" \/><\/code><\/blockquote>

    Naturally, I recommend that both<\/em> tags be used.<\/p>

    For Facebook<\/a>, images should be in the PNG<\/abbr> format, in JPEG<\/abbr> FIF<\/abbr>, or in GIF<\/abbr>; and be at least 50×50, with an aspect ratio no greater than 3-to-1. I don't know what might obtain elsewhere.<\/p>

    The same image file as is used for an Apple Touch icon might be quite suitable as the site thumbnail image.<\/p>

    Next:<\/span> Working Code and How to Use It<\/a><\/p>

    Comments<\/a><\/p>","protected":false},"excerpt":{"rendered":"This page is the first part of a discussion on supporting favicons, Apple Touch icons, and site thumbnail images. First, I'll try to explain the rôles and invocations of these images without peculiar reference to WordPress or to PHP. If you're already quite familiar with these three sorts of graphics and with the HTML to […]","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-4400","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/pages\/4400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4400"}],"version-history":[{"count":0,"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=\/wp\/v2\/pages\/4400\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.oeconomist.com\/blogs\/daniel\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}