Lovable favicon install runbook
Lovable spins up entire apps in minutes but rarely updates favicon sprites. Use this playbook to verify the current kit, export a new set, and make sure the hosted preview plus production deploy pick it up.
Preview parity
Lovable previews live on lovable.dev while production often lands on Vercel. Audit both so tabs never split icons again.
Share link safety
Force-refresh the Lovable share link after uploading new icons so marketing decks stop showing the default emoji grid.
URL finder for Lovable
Paste your Lovable preview link or production domain. We'll grab every favicon, let you choose one, and push it back to the generator.
Paste a domain and tap Scan to see every icon we can harvest.
We will open the generator with your selected favicon pre-loaded as the base image.
Playbook
Follow these beats whenever your builder regenerates UI so favicon coverage stays ahead of AI edits.
1Scan the Lovable URL
Paste the .lovable.dev preview domain into the URL finder below and capture every existing favicon.
2Push to generator
Send the cleanest asset into the generator, export the full Apple/Android/ICO matrix, and grab the manifest snippet.
3Update both repos
Upload icons inside Lovable's file manager AND commit them to the production repo so rebuilds stay consistent.
Checklist
Drop this straight into your deployment doc.
Add /lovable/favicon-install to your project README so each handoff includes the icon runbook.
Set a Lovable automation reminder to re-run this guide whenever a page section is rewritten.
Mirror the exported icons inside /public/icons and reference them through manifest.json.
Lovable favicon FAQ
Why does my Lovable app still show the default favicon?
Lovable serves the preview from lovable.dev and your published site from its own domain, and each caches icons separately. Replace the icon in the project files, republish, then hard-refresh both URLs before checking.
Where do favicon files go in a Lovable project?
Drop them in the public folder and reference them from the document head. Committing them to the connected GitHub repo is what makes them survive future Lovable regenerations.
Lovable install guide
Add /lovable/favicon-install to project README files, onboarding docs, and launch checklists so nobody skips the favicon step.