favicon, icon, and apple-icon in Next.js — Setting App Icons with Files or Code

Next.js supports special conventions for setting app icons: favicon, icon, and apple-icon. These icons appear in browser tabs, mobile home screens, and search engine previews. You can define them using image files or generate them programmatically with ImageResponse. This article explains both approaches, valid file locations, metadata configuration, and how Next.js automatically injects the correct <head> tags.

faviconapple-iconImageResponsehead tags

~2 دقیقه مطالعه · آخرین به‌روزرسانی ۷ آبان ۱۴۰۴

1. Types of App Icons in Next.js


Next.js supports three types of icons:

  • favicon: for browser tabs
  • icon: for general app branding
  • apple-icon: for iOS home screen shortcuts

2. Ways to Define Icons


You can define icons in two ways:

  1. Using image files (.ico, .jpg, .png)
  2. Generating icons with code (.js, .ts, .tsx)

3. Using Image Files


TypeSupported FormatsValid Location
favicon.icoOnly in app/
icon.ico, .jpg, .png, .svgAnywhere in app/**
apple-icon.jpg, .pngAnywhere in app/**

Example <head> Output:

<link rel="icon" href="/favicon.ico" sizes="any" />
<link rel="icon" href="/icon?...generated" type="image/png" sizes="32x32" />
<link rel="apple-touch-icon" href="/apple-icon?...generated" type="image/png" sizes="180x180" />

4. Generating Icons with Code


Use the ImageResponse API from next/og to generate icons programmatically:

// app/icon.tsx
import { ImageResponse } from 'next/og'

export const size = { width: 32, height: 32 }
export const contentType = 'image/png'

export default function Icon() {
  return new ImageResponse(
    <div style={{
      fontSize: 24,
      background: 'black',
      width: '100%',
      height: '100%',
      display: 'flex',
      alignItems: 'center',
      justifyContent: 'center',
      color: 'white',
    }}>
      A
    </div>,
    { ...size }
  )
}

Good to Know:

  • Generated icons are statically optimized at build time unless they use dynamic APIs
  • You cannot generate a favicon — use a .ico file instead
  • You can define multiple icons using numbered filenames like icon1.png, icon2.png

5. Input and Output Parameters


The default export function can receive dynamic route parameters:

export default async function Icon({ params }) {
  const { slug } = await params
}

Valid return types include:

  • Blob
  • ArrayBuffer
  • TypedArray
  • ReadableStream
  • Response

6. Metadata Configuration


You can export metadata for the icon:

export const size = { width: 32, height: 32 }
export const contentType = 'image/png'

Conclusion


Next.js offers flexible ways to define app icons using either static image files or dynamic code. With proper conventions and metadata, your icons will be automatically injected into the HTML head, ensuring a polished and recognizable experience across platforms.


نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

ادامه

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

ادامه

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

ادامه

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

ادامه

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

ادامه

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

ادامه