Most sites already have a logo. What they often do not have is a favicon package that actually works: a tab icon that stays readable at 16 pixels, an Apple touch icon that does not crop the mark off, a PNG set for modern browsers, and an .ico file for the stubborn cases. If you already have a square logo as SVG, PNG, JPG or even an old .ico, you do not need to start from a blank canvas. You need a complete set, generated from that file, and a quick check that the small sizes still look like your brand.

This is a practical walkthrough for turning an existing logo into a favicon package you can drop into a site.

Start with the cleanest master you have

The output cannot be sharper than the file you begin with.

  • SVG is the best master when you have one. It scales down without inventing pixels, and a simple mark (a letter, a monogram, a bold symbol) usually survives 16×16. An SVG full of fine strokes, thin serifs or a detailed illustration may still fall apart at tab size — but it is the right source to try first.
  • A large PNG (512 pixels or more, square, with a clear mark) is the next best thing. A tiny PNG already uploaded as a 32×32 favicon is a poor master; you will only be scaling mud.
  • JPG works if the logo sits on a solid background and is not a mess of compression artefacts. It cannot keep transparency, so a JPG logo on white will bring that white box with it unless you already flattened it on purpose.
  • An existing .ico can be unpacked and rebuilt if it is the only file you have left. Inspect it first. Many old .ico files contain only 16×16 and 32×32, which is not enough to produce a crisp 180-pixel Apple touch icon.

Prefer a version of the logo that is already a symbol, not the full wordmark. "Acme Consulting Ltd." set in a delicate typeface will become a blur in a browser tab. The letter mark or icon used on social avatars is usually the better favicon source.

Make it square, simple and padded

Before you generate anything, open the master and look at it as if it were a 16-pixel tab icon.

  • Crop to a square. A wide lockup will be letterboxed or crushed.
  • Give the mark a little padding. Browsers and home-screen masks crop the edges. A logo that touches every side will lose its corners, especially on Android's maskable icon shape or a rounded Apple touch icon.
  • Check contrast. A light mark on a transparent background disappears on a light tab bar. A dark mark disappears on a dark theme. If your logo is one colour, you may need a solid background or a second, simplified version just for the favicon.
  • Remove small tags, registered-trademark ticks and thin outlines that will vanish at 16 pixels.

If the only official logo fails this test, it is worth making a simplified favicon variant (a letter, a thicker monogram, a filled shape) rather than insisting the full logo must appear in the tab. The brand still reads if the mark is recognisable, not if every stroke is preserved.

Generate the whole package, not one file

A single favicon.ico in the site root used to be enough. Today you usually want a small set:

  • favicon.ico for older browsers and anything that still looks in the default place
  • PNG icons at the common sizes (at least 32 and 16, plus larger sizes for devices and shortcuts)
  • apple-touch-icon.png (typically 180×180) for iOS home screens
  • A maskable icon and a web app manifest if the site can be installed as a PWA

If your generator also hands you the HTML snippet and a manifest, use those as a starting point rather than inventing paths. Keep the filenames stable so you can replace the files later without editing every template.

When the source is already an .ico, convert it to PNG to see what is actually inside, then rebuild the set from a better master if the icons are soft. When the source is a SVG, you can still emit ICO and PNG companions — a single SVG favicon is supported in some browsers, but it is not a complete substitute for the rest of the package yet.

Check the small sizes before you ship

The failure mode is always the same: the 512-pixel preview looks great, and the 16-pixel tab looks like a smudge.

Open the generated 16×16 and 32×32 files at actual size, not zoomed in a design tool. If the mark is unreadable, go back to a simpler master and regenerate. Then check:

  • The Apple touch icon on a solid background, including whether padding is enough
  • Transparency: some contexts will put your icon on light grey, some on near-black
  • That you did not accidentally ship a JPG-style white box around a mark that should float

If your toolkit includes a preview of tab, search and home-screen sizes, use it. A favicon checker is also useful after you have uploaded the files, because a locally perfect package can still fail if a path 404s or an old icon is cached.

Install the files and keep the master

Put the generated files where the snippet says they should live, keep the SVG or large PNG master in version control, and do not overwrite it with a 32-pixel derivative. When the brand changes, you will want to rebuild the whole set from that master, then update the files in place — and often add a cache-busting query string or a new filename, because favicons are cached aggressively.

favicon.now can start from an image, SVG, or an existing ICO and give you the ICO, PNG, Apple and maskable icons plus a manifest and HTML snippet. The useful test is still the smallest size: if you cannot recognise the mark at 16 pixels, simplify the source and generate the package again.