---
title: Claude Code Favicon Install Guide
description: Generate and install a complete favicon and app icon set with Claude Code: give the agent a generator to run, then have it wire the head and commit the files.
canonical: https://favicontools.com/claude-code/favicon-install
---

# Claude Code Favicon Install Guide

Claude Code works in your terminal, so unlike a chat-only assistant it can run the tool that produces the image files, place them in the right directory, patch the head, and commit — in a single pass. The one thing it cannot do is invent PNG bytes, which is why the reliable pattern is giving it a generator to call.

## Why it matters

- **Give it a generator, not a description** — With a CLI, MCP server, or skill that emits real files, the whole job collapses into one turn: generate, install, patch, verify.
- **Write the convention down** — A line in CLAUDE.md about where icons live stops a future session from helpfully re-adding a starter template favicon link.

## Playbook

1. **Hand it the source** — Point at an emoji, a logo file in the repo, or an image URL, and say which environments you want covered.
2. **Let it install into the repo** — It should place files by framework convention, patch the head or the metadata export, and update manifest.json — reading the existing code rather than assuming a stack.
3. **Verify, then commit** — Ask it to run the dev server, request each icon path, and only then make a scoped commit containing the assets and the markup change.

## Checklist

- Add a CLAUDE.md note naming the generator, so regenerating the set is one instruction rather than an archaeology session.
- Keep the source logo or emoji reference in the repo alongside the output.
- Confirm the binaries landed in the commit — ignore rules covering images are the most common reason a deploy still serves the old icon.

## FAQ

### Can Claude Code make a favicon?

It can run tools that make one, but the model itself cannot emit binary image data. Install a favicon generator it can call — a CLI, an MCP server, or a skill — and it will handle generation, placement, and the head markup end to end.

### Why weren't the icon files included in the commit?

Almost always a .gitignore rule that matches images or the output directory. Run git status --ignored to see what was skipped, then add the paths explicitly with git add -f.

### Should icons go in app/ or public/?

In a Next.js App Router project, app/icon.png and app/apple-icon.png are detected automatically and are the least fragile choice. Keep favicon.ico in /public too, since some crawlers and link unfurlers still request that exact path.