Guide

How to Configure Favicons and App Icons in Next.js App Router (2026 Guide)

In Next.js App Router, place an icon.png, icon.ico, or icon.svg file inside your app/ directory for automated favicon detection. For dynamic theme-aware favicons, export an ImageResponse from app/icon.tsx with appropriate size and contentType exports.

Check favicons on any website

Install the FetchFavicon Chrome Extension to extract, preview, and validate favicons instantly.

Install Chrome Extension

When implementing nextjs metadata favicon, browsers evaluate link headers, display densities, and manifest definitions in a strict hierarchy. Desktop browsers prioritize high-DPI SVG or PNG declarations, falling back to /favicon.ico only when explicit markup is missing.

Modern specifications demand square aspect ratios and 32-bit RGBA transparency. Generate your multi-resolution bundle with our Favicon Generator, build legacy ICO files with the PNG to ICO converter, and verify adaptive theme rendering in our App Icon Preview studio.

How it works

  1. 1

    Prepare high-resolution square asset

    Start from a clean vector SVG or 512×512 PNG with transparent background.

  2. 2

    Generate optimized multi-resolution bundle

    Export a 16/32/48 multi-size .ico alongside dedicated 180×180 Apple touch and 192/512 manifest PNGs.

  3. 3

    Deploy to server root and verify headers

    Place favicon.ico at /favicon.ico and verify HTTP 200 response with correct MIME type.

Try it now

Generate and test your favicons now

Favicon Generator

FAQ

Why is my nextjs metadata favicon not updating after deployment?+

Browsers cache favicons aggressively in a dedicated internal database. Force refresh with Ctrl+F5, append ?v=2 to your asset path, or inspect the live URL in an incognito window.

Do I need both favicon.ico and SVG/PNG files?+

Yes. A multi-size favicon.ico provides 100% universal legacy fallback, while SVG and PNG files provide crisp scaling on Retina displays and PWA install prompts.

What happens if favicon.ico returns a 404 or 301 redirect?+

Search engine crawlers and browser address bars will fail to display the site icon in search snippets and tab bars. Icons should always return a direct HTTP 200 OK.

Related tools

Related guides

Guides →

Favicon & App Icon Benchmark: Platform Resolution & Format Compatibility Matrix
Platform / Context Required Resolution Optimal Format HTML / Manifest Declaration Performance Impact
Modern Browsers (Tabs & Bookmarks) Scalable Vector SVG (image/svg+xml) <link rel="icon" type="image/svg+xml"> < 2 KB (Fastest)
Legacy Browsers & Root Fallback 16×16, 32×32, 48×48 ICO (image/x-icon) <link rel="icon" href="/favicon.ico"> ~ 5-15 KB (Universal)
Apple iOS Safari (Home Screen) 180×180 px PNG (image/png) <link rel="apple-touch-icon"> ~ 15-25 KB (Crisp Retina)
PWA & Android Chrome 192×192, 512×512 PNG (image/png) site.webmanifest ("icons") Loaded on-demand only