Turn your logo or image into a complete favicon package. Preview it at real browser sizes, generate favicon.ico and PNG icons, download ready-to-use files, or check whether your website’s existing favicon is configured correctly.
Free • No signup required
Drop your logo here
PNG, JPG, WebP or GIF up to 5 MB. You can also paste an image from your clipboard.
Your image never leaves your browser. Everything here is processed on your own device.
RankNova’s free Favicon Generator converts your logo or image into ready-to-use website icons. Upload a PNG, JPG, WebP or GIF, zoom and reposition the artwork, adjust padding and background, preview your favicon at real browser sizes, and download the complete favicon package.
Everything runs in your browser, so your image is never uploaded to a server. Already have a favicon? Use the Website Favicon Checker to find missing files, unreachable icon URLs, unexpected dimensions and common implementation problems.
One upload produces a complete favicon package: a real multi-size favicon.ico, PNG icons for browser and web app use, an Apple touch icon, and a web app manifest.
| File | Size | Purpose |
|---|---|---|
favicon.ico | 16×16, 32×32 and 48×48 in one file | Traditional browser favicon, served from your site root |
favicon-16x16.png | 16×16 | Small browser and interface icon |
favicon-32x32.png | 32×32 | Browser and interface icon |
favicon-48x48.png | 48×48 | Higher-resolution faviconIncluded by default. You can switch it off before generating. |
apple-touch-icon.png | 180×180 | Apple touch icon |
android-chrome-192x192.png | 192×192 | Web app icon |
android-chrome-512x512.png | 512×512 | Large web app icon |
site.webmanifest | — | Web app metadata referencing the 192×192 and 512×512 icons |
Not every browser needs every file. The package covers the common surfaces, and you reference the ones your site needs.
There is no single favicon size that covers every use case. Small icons such as 16×16 and 32×32 remain useful for browser interfaces, while larger assets are used for touch icons, higher-resolution displays and web app experiences. Generating several sizes from one source is the practical approach.
| Size | Typical use |
|---|---|
| 16×16 | Small browser and interface use |
| 32×32 | Browser and interface use |
| 48×48 | Higher-resolution and compatibility use |
| 180×180 | Apple Touch Icon |
| 192×192 | Web app icon |
| 512×512 | Large web app icon |
You do not need to reference every size manually. A site root favicon.ico, a couple of PNG sizes, the Apple touch icon and a manifest cover most cases.
Google requires a favicon to have a square 1:1 aspect ratio and be at least 8×8 pixels, and recommends using a favicon larger than 48×48 pixels so it appears clearly across supported surfaces.
Meeting these requirements makes a favicon eligible, but it does not guarantee that Google will display it in search results.
Upload an image, adjust how it sits on a square canvas, check it at small sizes, generate the package and install the files. Five steps, all in the browser.
Upload your image
Choose your logo, icon or another square-friendly image. PNG, JPG, WebP and GIF files up to 5 MB are supported, and you can drag a file in or paste one from your clipboard.
Adjust your favicon
Zoom and reposition the artwork inside the square canvas, add safe padding, and either keep transparency or set a background colour. You can also clear a flat background colour from the image itself.
Preview small sizes
Check the design at real favicon sizes. The 16×16 and 32×32 previews are shown at actual size next to a magnified view, so you can see which details survive.
Generate the package
RankNova encodes a real multi-size favicon.ico plus the PNG icons, the Apple touch icon, the web app icons and site.webmanifest.
Download and install
Download the ZIP or individual files, upload them to your site, then add the generated link elements to your pages.
ICO is the traditional multi-size favicon format, PNG is the practical choice for individual sizes, and SVG scales to any size but is not supported everywhere.
Traditional favicon format that can hold several icon sizes in a single file.
Still worth serving at your site root, because browsers request /favicon.ico whether or not a link element points to it. RankNova writes a real ICO containing 16×16, 32×32 and 48×48 images rather than renaming a PNG.
Common raster format with predictable dimensions and transparency support.
The practical choice for every size you reference explicitly. RankNova generates PNG icons for browser use, the Apple touch icon and the web app icons.
Resolution-independent vector format supported as a favicon by compatible browsers.
Browser support is not universal, so an SVG favicon is best offered alongside ICO and PNG rather than instead of them. RankNova does not generate SVG favicons, and does not accept SVG uploads, because rendering untrusted SVG in the browser carries script and remote resource risks.
RankNova generates ICO and PNG assets. That combination covers browser tabs, bookmarks, Apple touch icons and web app icons without relying on format support that varies by browser.
Upload the generated files to your site, then place these link elements inside the document head. They match the filenames RankNova produces.
<link rel="icon" href="/favicon.ico" sizes="any">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="apple-touch-icon" href="/apple-touch-icon.png">
<link rel="manifest" href="/site.webmanifest">Upload the generated files to the appropriate public location for your website, so that favicon.ico answers at your site root. File paths differ between frameworks and content management systems, so adjust them to match your setup. After generating a package, the tool above also shows install steps for Next.js, React with Vite, and WordPress.
Creating a favicon is only half the job. RankNova can also inspect your website to find the favicon references in your HTML and manifest, check whether those files are publicly reachable, read the format and dimensions of each icon it retrieves, and identify common implementation problems.
A favicon usually fails to appear because the browser or search engine cannot find or use the configured file. Caching is one common cause, but it is worth ruling out the others first.
Incorrect favicon path
The link element points somewhere the file is not, often a path that worked locally but not once deployed.
Broken favicon URL or 404 response
The referenced file is not there. Opening the favicon URL directly is the quickest way to confirm what your server actually returns.
Missing HTML favicon reference
No link element declares an icon, so browsers fall back to requesting /favicon.ico from the site root and nothing else.
Invalid or unreadable image file
The file exists but is not a valid image, for example a PNG renamed to .ico, or an HTML error page served where an image was expected.
Deployment problem
The files were never uploaded, landed in the wrong directory, or are excluded from the published build output.
Old cached favicon
Browsers cache favicons aggressively. This is a common cause, but it is worth ruling out the others before assuming it.
Manifest references icons that are missing
site.webmanifest lists icon paths that do not resolve, so installed and home screen experiences have nothing to use.
Favicon URL is not publicly accessible
Authentication, an IP restriction or a robots rule prevents the file being fetched by anything other than a signed-in browser.
Verify that:
Favicon updates are not immediate. The change takes effect only after Google recrawls your home page, which can take anywhere from several days to several weeks depending on how often Google refreshes your site. Even when every requirement is met, Google does not guarantee that a favicon will be displayed. If your icons are missing or unreachable, the checker above will show which ones, or you can check your website crawlability to confirm search engines can reach your pages at all.
A favicon should not be treated as a direct Google ranking factor. Its primary benefits are website identification, branding and consistent visual presentation across browser and supported search interfaces. Google may display an eligible favicon alongside a site’s organic search result, but favicon appearance is controlled by Google and is not guaranteed.
If you are working through on-page signals that do affect how your pages are understood, analyze your meta tags next.
A favicon is a small icon that represents a website. It is commonly used in browser tabs, bookmarks and other browser or search interfaces to help users visually identify a site.
Upload a PNG, JPG, WebP or GIF to RankNova's Favicon Generator. Zoom and reposition the artwork inside the square canvas, add padding, choose a background or keep transparency, preview the icon at real favicon sizes, then generate and download the favicon package.
Different platforms use different icon sizes, so generating several is useful. Common website assets include 16×16, 32×32 and 48×48 icons, while larger sizes such as 180×180, 192×192 and 512×512 are used for touch and web app experiences.
Google requires a favicon to be square and at least 8×8 pixels, and recommends using a favicon larger than 48×48 pixels so it looks good across supported surfaces. Meeting the requirements does not guarantee that Google will display the favicon in search results.
Yes. RankNova uses your uploaded image as the source and generates a real .ico file containing 16×16, 32×32 and 48×48 images, alongside the PNG favicon sizes. It does not simply rename a PNG, because ICO is a distinct container format with its own directory structure.
A square 1:1 source is the safest choice. RankNova renders onto a square canvas, so you can zoom, reposition and pad a non-square image until it sits correctly. Google Search specifically requires a square favicon for favicon eligibility.
Yes. PNG preserves transparency, which suits logos that should not sit on a fixed background. Preview transparent icons against both light and dark backgrounds to check they stay visible. One exception: Apple touch icons ignore transparency and are composited onto black, so RankNova always gives that icon a solid background.
ICO is the traditional favicon format and can contain multiple icon sizes in one file. PNG provides predictable dimensions, good image quality and transparency support. Websites commonly provide both: an ICO at the site root, and PNG icons referenced explicitly for each size.
An Apple Touch Icon is the image used on applicable Apple devices when a website is saved or added to the home screen. RankNova generates a 180×180 apple-touch-icon.png as part of the package.
Common causes include an incorrect file path, a missing or broken image, an invalid HTML favicon reference, a deployment problem or cached favicon data. Use RankNova's Website Favicon Checker to inspect the favicon references on your live site and identify which files are missing, unreachable or invalid.
Check that Googlebot can crawl your home page, that Googlebot-Image can crawl the favicon file, that the image is square and meets Google's current requirements, and that the favicon URL stays stable. Changes take effect only after Google recrawls your home page, which can take anywhere from several days to several weeks. Favicon display is not guaranteed even when every requirement is met.
A favicon is not a direct ranking factor. Its main value is website recognition, branding and consistent presentation across browser and supported search interfaces. Google can display eligible favicons beside search results, but meeting the favicon requirements does not guarantee display or improve rankings.
A favicon is one small detail. RankNova audits the technical SEO, content and AI readiness signals across your whole website.