Skip to content
Frisbly
Favicon generator

Generate a complete favicon pack in your browser.

Drop a PNG, JPEG, or AVIF source and download ICO, PNG icons, Apple Touch Icon, and site.webmanifest as a ZIP. The file is not uploaded.

Drop an image here

Choose file

PNG, JPEG, or AVIF ยท max 5 MB ยท up to 16 MP

Square source recommended ยท transparent PNG recommended for clean edges

This action = 2 credits

Waiting for an image.

Checking credit balance...

Checking credit balance...

How to use it

  1. 1

    Choose a source image

    Start with a square logo or icon image from your device. The source file is opened in the browser rather than uploaded to a server.

  2. 2

    Review icon outputs

    Generate browser-ready sizes for favicon use, app icons, Apple Touch Icon, and web manifest references from the same source.

  3. 3

    Check visual clarity

    Inspect whether the mark still reads at small sizes. Simple shapes and strong contrast usually work better than detailed artwork.

  4. 4

    Download the package

    Export the generated icon files and manifest assets for your site folder, framework public directory, or deployment checklist.

Common use cases

New site setup

Prepare favicon and app icon assets during a launch checklist so browser tabs, bookmarks, mobile shortcuts, and install prompts use a consistent mark.

Brand refresh updates

Regenerate icon sizes after a logo adjustment without sending internal brand drafts to a remote conversion queue. This keeps the review loop local until the final assets are ready.

Static and framework projects

Create the files commonly copied into static site, Next.js, or Vite public folders. Having the package ready reduces missed favicon sizes during deployment.

Security and privacy

Local favicon generation

Favicon generation is handled in the browser and does not require uploading the source logo or draft artwork to a server route. Frisbly does not need account data, filenames, EXIF data, or user identifiers to create the package. The generated files are downloaded to your device, where you decide which assets become part of the deployed site.

Supported inputs and outputs

Supported favicon outputs

  • Local PNG, JPEG, WebP, or SVG-style source artwork where supported by the browser.
  • ICO and PNG favicon assets for browser tabs and bookmarks.
  • Apple Touch Icon output for home-screen shortcuts.
  • Web manifest file references for installable site metadata.

FAQ

Is my logo uploaded to generate favicons?

No. The source artwork is processed in the browser, so a server upload is not required for the generated icon package.

What source image works best?

A square image with a clear mark, strong contrast, and limited detail usually produces better small favicons than a complex full logo.

Do I need both ICO and PNG files?

Many sites include both. ICO helps cover traditional favicon support, while PNG sizes and Apple Touch Icon files cover modern browser and device surfaces.

Where should I place the files?

Most projects place generated assets in the public or static folder, then reference the favicon and manifest from the document head or framework metadata configuration.

Can I regenerate icons after a brand update?

Yes. Open the new source artwork, generate a fresh package, and replace the deployed files when the updated mark is approved.

SVG cleanupImage compressionImage Editor
Related
SVG cleanupBase64 encoder decoderImage color adjust