Skip to main content
What you’ll learn
By the end of this guide, you’ll be able to:
  • Define a complete farcaster.json manifest that meets Base App requirements.
  • Map each manifest property to its role in search, discovery, and embeds.
  • Validate images, text, and URLs against required constraints.
  • Link your manifest to your domain using accountAssociation.
  • Control indexing for staging and production with noindex.

Overview

Your /.well-known/farcaster.json file is the manifest for your Mini App. It contains all the metadata Base App uses to:
  • Display your app in search results, trending sections, and category listings
  • Generate rich, clickable embeds when your app is shared
  • Show your app in users’ saved apps for quick access
If the manifest is missing, incomplete, or invalid, your app won’t appear in Base App discovery features.

Location

Serve your manifest over HTTPS at:
Serve with Content-Type: application/json and ensure the file is publicly accessible (no auth).

How Base App uses Manifest

  • Search indexing: Your app appears in search after it has been shared at least once. Indexing typically completes in ~10 minutes.
  • Category placement: primaryCategory determines where your app appears in category browsing. tags improve cross-surface visibility and filtering.
  • Embeds: Open Graph fields (ogTitle, ogDescription, ogImageUrl) and heroImageUrl power compelling feed previews that drive clicks.
  • Saved apps: name and iconUrl appear when users save your Mini App for quick access.
If your Mini App does not show in search, follow the debugging guide here.

Example manifest

For a visual mapping of how fields render, see the Mini App specification reference.

Field reference

Top-level fields

accountAssociation fields

frame fields

Identity & Launch

Defines your Mini App’s core identity and the URL users land on when they open it.

Loading Experience

Controls the splash screen visuals and colors shown while your Mini App loads.
Determines how your Mini App is indexed, categorized, and surfaced across Base App discovery features.

Display Information

Provides the descriptive text, screenshots, and promotional images shown on your Mini App’s profile.

Embeds & Social Sharing

Configures how your Mini App appears when shared in feeds or on social platforms.

Advanced Capabilities

Specifies technical integrations, event handling, and special permissions your Mini App requires.
Choose your primaryCategory carefully — it determines where your app appears in Base App’s category browsing and rankings.

Validation checklist

  • Manifest is served over HTTPS at /.well-known/farcaster.json
  • All required fields are present
  • Image sizes match the constraints (icon, OG, hero, screenshots)
  • Text fields respect character and formatting limits
  • "noindex": true is used only for staging/development
Test your manifest with a simple curl to confirm accessibility and headers: curl -sI https://your-domain.com/.well-known/farcaster.json.

Development vs. production

  • Set "noindex": true for development or staging environments to prevent search indexing.
  • Remove or set "noindex": false for production so users can discover your app.
Your app appears in search after the first share is detected. Indexing usually completes in ~10 minutes.

Common issues

  • Missing required fields → app won’t index in search
  • Image format/size mismatches → broken or distorted embeds
  • Invalid primaryCategory → app won’t appear in category browsing
  • Overlong strings → truncation or rejection at indexing
  • Manifest not publicly accessible → discovery fails

Next steps