Analytics cookies
We use optional Google Analytics to understand which tools are useful and improve the site. Analytics stays off unless you accept. Privacy Policy
What’s in the pack
One image becomes 10 files: favicon.ico, PNG favicons at 16, 32 and 48 px, a 180 px Apple touch icon, 192 and 512 px Android icons, matching maskable icons and a site.webmanifest that lists them.
favicon.ico holds the 16, 32 and 48 px icons as PNG images inside one ICO file, which every current browser reads. Every icon is drawn once at 1024 px and reduced in halving steps, so even the 16 px favicon stays smooth and all the files match.
Maskable icons and the safe zone
Android launchers crop maskable icons to their own shape: a circle, a squircle, a rounded square and others. The Web App Manifest specification defines a safe zone that every shape keeps: a circle in the middle of the icon, with a radius of 40% of its width.
The preview shows that circle and the tool checks whether any visible artwork falls outside it. That check is a visual aid based on the pixels, not an official validation: only you know which parts of the artwork matter. Maskable icons get their own padding and always use the background color, so they stay full squares behind any mask.
Installing the icons
Unzip the pack into your site’s root folder, then add the HTML from the tool to the <head> of every page. If your site already has a web manifest, add the icons from site.webmanifest to it instead of linking a second one. Images up to 8192 px on each side are accepted; an SVG or a square image of 512 px or more gives the sharpest result.
Your image stays on your device
Your image stays in your browser. Icons are made on your device; nothing is uploaded. The image is read, drawn and packed into a ZIP by your browser, and is never sent to GetKineticHub. SVG files are checked first and refused if they contain scripts or link to anything outside the file, so adding one never makes a network request.
If you accept optional analytics, the tool reports only that a download, share or copy finished and its file type, such as ZIP or PNG. Your image, its name and the names you type are never included.
Frequently asked questions
Do I still need favicon.ico?
It’s worth keeping. Browsers use the icons linked in your page’s <head>, but some browsers, feed readers and other tools still request /favicon.ico from the site root without reading any tags.
Why don’t I see my new favicon?
Browsers cache favicons separately from pages and can keep showing an old one for a while. Reload without the cache, open the icon’s address directly, or check in a private window. Also check that the files are in the site root, where the tags expect them.
Does the pack include an SVG favicon?
No. It contains ICO and PNG files and a web manifest; an SVG source is drawn into each PNG size. To serve your SVG as well, add it with its own <link rel="icon" type="image/svg+xml"> tag, and browsers that support SVG favicons can use it.
Do I need this pack for a WordPress site?
Not always. WordPress can make its own icons from one square image of at least 512 × 512 px set as the Site Icon. The pack suits sites where you want every file under your control, including maskable icons and a manifest. Use one approach or the other, so two sets of icon tags don’t compete.