Base44 favicon install runbook
Base44 builds and hosts the app for you, so there is no local repo to drop icons into — they have to arrive through the builder and then survive the next publish. Think of it as two separate jobs: get real image files hosted, and get explicit icon tags into the document head.
Prompts can rewrite the head
Because you change the app by describing changes, a redesign request can regenerate the page shell and take the icon tags with it.
Preview and published differ
The version you are iterating on and the version your users load are different URLs with different caches. Judge the icon on the published one.
URL finder for Base44
Paste your Base44 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.
1Export the whole set first
Generate every size in one go. Uploading through a builder is slow enough that you do not want to discover a missing Apple touch icon later.
2Bring the files into the app
Upload the icons as app assets, then ask the builder to reference them by URL with explicit icon, apple-touch-icon, and manifest tags in the head.
3Publish, then check the real domain
Load the published app — and your custom domain if one is attached — in a private window to confirm the tab icon actually changed.
Checklist
Drop this straight into your deployment doc.
Ask the builder to show you the head markup it generated so you can confirm each referenced URL resolves.
Store the square master image outside Base44 so you can regenerate without re-cropping.
Re-check the icons after any prompt that changes branding, layout, or the page shell.
Base44 favicon FAQ
How do I change the favicon in a Base44 app?
Through the builder rather than a file manager: upload the icon as an app asset and instruct the builder to link it from the document head. Then publish, because settings and assets only reach visitors on the next deploy.
Why does my Base44 app show a blank or generic tab icon?
When no icon link is present, the browser falls back to requesting /favicon.ico, and if nothing is served there you get the generic document icon. Adding an explicit link tag to a file you know is reachable fixes it immediately.
Base44 install guide
Add /base44/favicon-install to project README files, onboarding docs, and launch checklists so nobody skips the favicon step.