Troubleshooting

Symptom-based fixes for export, install, and editor issues.

Work through the symptom that matches what you see. Each section lists checks in order — stop when the issue is resolved.

Browser favicon still shows the old icon

Browsers cache favicons aggressively. A successful install can still look unchanged in the same tab.

Checks:

  1. Hard refresh — ⌘+Shift+R / Ctrl+Shift+R.
  2. Open the site in a private window (no cache).
  3. Confirm the new files are actually deployed — fetch /favicon.ico and /icon.svg directly; timestamps or file contents should match the export.
  4. While iterating locally, cache-bust: icon.svg?v=2 in your <head> snippet.
  5. Inspect <head> in DevTools → Elements — verify rel="icon" and rel="apple-touch-icon" href values point at the paths you installed.

Not the fix: Redesigning at 512px when the problem is only visible at 16px — see Editor Guide.

PWA manifest icon missing or wrong

Checks:

  1. DevTools → ApplicationManifest — confirm the manifest parses with no errors.
  2. Icon src paths in manifest.webmanifest must be absolute (start with /).
  3. Confirm manifest.webmanifest is served with a manifest MIME type (application/manifest+json or application/json). Vercel and Next.js handle this by default; some static hosts need a manual override.
  4. Confirm icon-192.png and icon-512.png return 200 at the paths listed in the manifest.
  5. For Android adaptive icons, confirm icon-512-maskable.png is listed with "purpose": "maskable".

Install reference: Web Assets.

iOS home screen icon missing or wrong

Checks:

  1. Confirm apple-touch-icon.png is at the site root or linked explicitly:
    <link rel="apple-touch-icon" href="/apple-touch-icon.png">
  2. iOS ignores SVG favicons for Add to Home Screen — you need the 180×180 PNG from Web Assets.
  3. Test on a real device; the Preview mockup is approximate.

iOS applies its own mask and rounding. Verify on-device, not only in the editor.

Font looks wrong in the editor

Symptom: Changing font family or weight appears to do nothing.

Checks:

  1. The Google Font may not have loaded — refresh and try again.
  2. Pick a different family temporarily to confirm the control is working.
  3. Use a heavier weight (600–800) for small-size text motifs.

Editor preview depends on live font loading. See Typography & Fonts.

Font or text looks wrong in exported files

Symptom: Export succeeds but text motifs look like a fallback font or are missing detail.

Checks:

  1. Confirm the font loaded in the editor before export (preview should match the chosen family).
  2. Try a simpler family — very light weights and thin serifs often fail small-size readability even when outlining succeeds.
  3. Export again after a full page refresh so the font file fetch completes.
  4. If export fails outright, try a different font — the outline step fetches the font binary from /api/google-font-file; a failed fetch aborts conversion for that node.

Text is converted from <text> to <path> on export so the output does not depend on system fonts.

Export fails or hangs

Checks:

  1. Note the error toast message, then refresh and retry once.
  2. For text motifs, try a different Google Font — font fetch or outline conversion can fail on edge cases.
  3. For Custom SVG Upload, confirm the asset passed import validation (no external references, within size limits).
  4. Sign in if the failure mentions Custom SVG Upload or Optimized Exports — some paths require authentication.

If the design works in preview but export repeatedly fails, use Send Feedback in the header with the motif type and format you selected.

Download blocked or missing

Checks:

  1. Check the browser's Downloads list — the file may have saved without a prominent prompt.
  2. Disable Ask where to save each file temporarily if the browser blocks automatic downloads.
  3. Confirm no extension is blocking downloads from app.favycons.com.
  4. Retry in a private window to rule out extension interference.

URL loads defaults instead of the shared design

Symptom: Opening an iconconfig link shows the default design and a warning banner.

Checks:

  1. Confirm the URL uses iconconfig, not legacy params (icon=, bgColor=, …) — those are no longer supported.
  2. Re-encode from the source IconSettings JSON — see Load from URL.
  3. Check URL length — very large configs can exceed client limits.

"Free plan limit reached"

Free plan caps saved designs at 5. Delete a design from My Designs or upgrade. Session auto-save in the browser is separate and not counted toward the limit.

Pro caps saved designs at 1,000 and unlocks additional Pro features. If an iOS, Android, Desktop, or Raycast guide is unavailable, that Export Target is not currently shown in the app.

See Saving & Accounts.