BriskFile

Favicon generator

One image in, a complete icon set out — including a genuine multi-size favicon.ico, not a PNG with the extension changed. Generated on your device.

Nothing is uploaded. Your logo is read by this page and processed by your own processor.

A favicon set needs 16, 32 and 48 pixel images inside favicon.ico, plus 180, 192 and 512 pixel PNGs referenced from your web manifest.

Why one PNG is not enough

A 16 × 16 tab icon and a 512 × 512 splash icon are not the same picture scaled — they are different pictures. Fine detail that reads beautifully at 512 becomes noise at 16, which is why serious brands draw a simplified mark for the small sizes.

What a generator can do is make sure the file format is right at every size, and that is where most go wrong. ICO is a container: a directory header followed by several complete images. Renaming logo.png to favicon.ico produces a file with no such header. Some browsers sniff the content and display it anyway, which is exactly why the mistake persists — it appears to work until somebody pins your site to a Windows taskbar.

What BriskFile produces

  • favicon.ico — 16, 32 and 48 pixels in one properly structured container.
  • apple-touch-icon.png — 180 pixels, used when an iPhone adds your site to the home screen.
  • icon-192.png and icon-512.png — referenced from the web manifest, used by Android and for splash screens.

The PNGs inside the ICO are stored as PNG rather than the older BMP-with-mask layout. Every Windows version since Vista and every current browser reads that; the BMP form only matters for Windows XP and roughly triples the file size.

A note on transparency

iOS ignores transparency on home-screen icons and composites them onto black, so a transparent apple-touch-icon gets a black background rather than a white one. If your mark is dark, give it a solid background before generating.

Questions

What size should a favicon be?

A real favicon.ico holds several sizes at once — 16, 32 and 48 pixels. On top of that, modern browsers and phones take PNGs from your web manifest, usually 180, 192 and 512 pixels. This generator produces all of them from one image.

Can I just rename a PNG to .ico?

No. ICO is a container format with its own header describing each image inside it. A renamed PNG has no such header, and Windows will refuse it — though confusingly some browsers accept it, which is why the mistake survives so long.

Do I still need favicon.ico at all?

Yes, in practice. Browsers request /favicon.ico from your site root by default even when you have declared PNG icons, and feed readers and older bookmark bars rely on it. It costs a couple of kilobytes.

Why does my icon look muddy at 16 pixels?

Because 16 × 16 is 256 pixels in total. Detailed logos turn to mush at that size no matter how they are scaled — the fix is a simplified mark for the small sizes, not a better resampler.

Is my logo uploaded?

No. Every size is generated in your browser by your own processor, and the ICO is assembled in memory. An unreleased logo is exactly the kind of file that should not be sent to somebody else’s server.

What BriskFile will not do to you

  • Your files never leave your device

    Every conversion runs in your browser. Open DevTools, watch the Network tab, and you will see no upload — because there is not one.

  • No account, no email, no watermark

    Nothing to sign up for and nothing stamped on your images. There is no step between choosing a file and getting it back.

  • No limits at the download button

    No daily cap, no file counter, no "upgrade to download". If the tool starts a job, it finishes it.

  • Checkable, not just claimed

    Open the Network tab and convert something — nothing goes out. Or load the page, disconnect, and watch it keep working: the tool is already on your machine, and your file never leaves it.