Skip to content
Motifuse

Browser-based · Favicon and app icons

Build every icon. Check it at 16px.

One source becomes a real ICO, a scalable SVG, Apple and PWA PNGs and a manifest that validates. Motifuse previews the tiny crop and the maskable safe zone before you ship, and builds the package in this browser.

Icon production

Create, preview, validate and export

Runs locally
Untitled icon Autosaved
Add artwork to beginUpload a file, or load the demo artwork from the source panel.
1024×1024 master
Shared artwork and defaultsScale 88% · Padding 10% · 100% zoom

Actual size

  • 16
  • 20
  • 24
  • 32
  • 48
  • 64
Ready to export7/7 checks passed10 files in packageManifest valid
  • Runs locally
  • No account required
  • Open standards
  • Works offline

Simple process

From artwork to a deployed favicon

The installation code in the workspace uses the same filenames and path prefix as the package, so the handoff cannot drift away from the files you download.

  1. 01

    Create

    Upload artwork, type a monogram, choose a symbol, or render an emoji. The source is normalized on a 1024px square canvas without being stretched.

  2. 02

    Review

    Tune the base artwork, then inspect the tiny browser crop, Apple surface, PWA icon, maskable safe zone, and optional dark version.

  3. 03

    Export

    Choose a modern, minimal, PWA, legacy, or custom package. Every PNG, the multi-image ICO, manifest and README are built in this browser.

  4. 04

    Install and verify

    Copy the framework-specific snippet, deploy the files at the chosen path, then check direct URLs and the live page.

Built for every surface

One mark.Every crop it needs.

A logo that works on a website is not automatically a favicon. Tiny tabs need less detail, Apple icons need breathing room, and maskable icons need bleed around a protected centre.

Four ways inUpload artwork, type a monogram, choose a symbol or render an emoji — all normalised on one 1024px square.
A genuine ICO containerSeparate 16, 32 and 48px entries in one file, rather than a PNG given an .ico extension.
Hand-tuned per surfaceThe tiny crop, the Apple padding and the maskable bleed are separate decisions, because one crop does not fit all.
The maskable safe zoneA centred circle at 40% of the width, drawn over your icon, so clipping is visible before a platform does it.
A manifest that validatesEvery src resolves, every size matches the real PNG, and purpose is set — kept in sync with the files in the ZIP.
Framework install snippetsGenerated from your chosen path prefix and the exact filenames in the package, so the handoff cannot drift.
Optional dark variantA second icon for dark tab bars, declared behind prefers-color-scheme with a normal fallback kept.
Local processingDecode, sanitise, resize, encode and zip all run in this tab. Only the separate live-site checker touches the network.

One source, every surface

Where a favicon actually appears.

A favicon is not only the tiny mark in a tab. The same identity is requested by bookmarks, search results, saved home-screen shortcuts and installable web apps — and each of these previews carries your own icon.

  • Browser tabs

    16 and 32px demand a bold silhouette.

  • Bookmarks and history

    A recognizable mark helps people find their way back.

  • Search results

    A square, crawlable icon can represent the hostname.

  • Apple home screens

    A larger icon needs an opaque, optically balanced crop.

  • PWA launchers

    Standard and maskable purposes serve different platform treatments.

  • Light and dark themes

    Transparent artwork has to remain visible on both tab bars.

One logo does not fit every surface automatically

Tiny browser icon

  • Increase optical scale without stretching.
  • Remove transparent margins and fragile detail.
  • Judge the true 16px raster, not a large mockup.

Adaptive install icon

  • Keep important artwork inside the 40%-radius safe zone.
  • Use an opaque, full-bleed background.
  • Test more than one possible platform mask.

Production package

What the ZIP contains.

The recommended preset stays intentionally small. Legacy files are available separately instead of being presented as universally required.

Every file in the package, what requests it, and when to include it
FileDimensionsUsed byWhen to include
favicon.ico16, 32, 48Browser fallback and direct root requestsRecommended
favicon.svgScalableModern browser tabsRecommended
favicon-32x32.png32×32Browser tabs and bookmarksRecommended
favicon-48x48.png48×48Search and browser UIRecommended
apple-touch-icon.png180×180Apple home-screen shortcutsRecommended
icon-192.png192×192PWA and Android install surfacesFor installable apps
icon-512.png512×512PWA install and launch surfacesFor installable apps
icon-maskable-*.png192, 512Adaptive platform masksFor maskable PWA
site.webmanifestJSONInstall metadata and icon declarationsFor installable apps

Practical validation

Catch favicon problems before your visitors do.

The Studio reports checks with a reason and a direct next action. It does not collapse unrelated technical checks into an unexplained score.

Transparent margins

A mathematically centered logo can still look tiny if invisible pixels surround it.

Unsafe maskable crop

Adaptive shapes can clip corners even when a square preview appears fine.

Broken paths

A valid manifest is not useful when its icon URLs resolve relative to the wrong directory.

Conflicting declarations

Themes and frameworks sometimes inject a second favicon that wins browser selection.

Incorrect MIME type

A server can return HTML for an icon path and still respond with a misleading 200 status.

Aggressive caching

A correct deployment can appear stale in browser chrome and search results for very different reasons.

Diagnostics

Troubleshooting common favicon failures.

Almost all of these are caching, a mask, or a path — and each one has a specific check rather than a suggestion to try again later.

  • No upload
  • No account
  • No watermark
  • Nothing leaves this device

Privacy by design

Your source artwork stays in this browser.

Uploads are decoded, sanitized when they are SVG, resized, encoded and zipped on this device. Object URLs are released when artwork or previews change. No source image, filename, SVG source or generated package is sent to analytics.

The live-site checker is the exception. Cross-origin browser rules require Motifuse to fetch the public URL on your behalf. That endpoint accepts only public web addresses, validates DNS and every redirect, caps response sizes, applies timeouts, and returns parsed favicon metadata rather than remote page content. It never receives your source artwork.

Nothing is uploaded

Decoding, resizing, ICO assembly and ZIP packaging all run in this tab. There is no submit step for your artwork.

Files are read on your device

The File API reads a selected image locally. The bytes go from your disk into this tab's memory and no further.

SVG sources are sanitized

Scripts and external references are stripped before a vector source is rendered, because an SVG is a document, not just a picture.

Object URLs are released

Preview blobs are revoked when artwork changes, so a long session does not accumulate copies of your icon in memory.

Nothing identifying is in analytics

An export records that it ran and which preset. Never the filename, the artwork, or the generated package.

Your work is kept in this browser

So a refresh does not lose it, the studio saves the project — and the source artwork when it is small enough — to this device's local storage. It is never sent anywhere. Clear saved in the toolbar deletes it, and New replaces it.

FAQ

Answers for designers and developers

Got a logo that needs to survive 16 pixels?

Drop it above and check the tab crop, the Apple surface and the maskable safe zone before you export.

Try another image tool