---
title: GitHub Copilot Favicon Install Guide
description: Add a favicon with GitHub Copilot: agent mode or the coding agent. Get real image files into the repo, let it wire the head and manifest, and review the PR.
canonical: https://favicontools.com/copilot/favicon-install
---

# GitHub Copilot Favicon Install Guide

Copilot has two ways to touch your repo: agent mode in the editor, which edits files you can watch, and the coding agent, which runs in a GitHub Actions runner and opens a pull request. Neither can render a PNG. The editor path wants real files already in the tree; the Actions path wants the source committed and the resulting PR read before you merge.

## Why it matters

- **Two modes, one blind spot** — Agent mode in the IDE and the Actions-based coding agent both wire markup well and both output text, not image bytes. Bring the files; give either one the wiring.
- **The coding agent runs in Actions** — It works in an ephemeral runner from your committed code, so a logo it needs must be in the repo, and its output arrives as a PR you have to review, not a running site.

## Playbook

1. **Get real files into the repo** — Generate the full kit and commit it, or commit the source logo so the Actions runner can reach it. The model won't produce the binaries and the runner won't fetch them from a prompt.
2. **Give one wiring instruction** — Name the files and sizes and tell Copilot to reference them following the repo's existing convention (the head or metadata export plus manifest.json) and nothing else.
3. **Review the PR, check the binaries** — For the coding agent, open the PR's Files changed and confirm the .ico and .png files are present, not only the link tags. For agent mode, read the diff before you accept it.

## Checklist

- Note in .github/copilot-instructions.md that icons are generated binaries the agent must not recreate.
- Confirm the image files landed in the PR or the accepted diff. An ignore rule on binaries is the usual reason they don't.
- Load the page in a private window after merge; Copilot verifies code, not the rendered tab.

## FAQ

### Can GitHub Copilot generate a favicon image?

No. Both agent mode and the coding agent edit text and run commands, but the model cannot emit PNG or ICO bytes. Generate the icons with a real tool, put them in the repo, and let Copilot handle the head markup and the manifest.

### The coding agent opened a PR but the icon is still blank. Why?

Check that the image files are in the PR, not just the markup. The Actions runner works from committed code, so a source image referenced only in the prompt, or binaries caught by a .gitignore rule, leaves the link tags pointing at nothing.

### Where should icon files go?

By framework: app/icon.png for Next.js App Router, public/ plus explicit link tags for Vite and most SPAs, with favicon.ico at the root for crawlers that request it by path. Copilot can read the repo and tell you which applies.