Skip to content
Aback Tools Logo

Expo Config Reference

Search 24 app.json and app.config.js fields by platform, requirement level, and category. Copy field keys instantly, review example values, and export filtered reference data for faster Expo setup and release workflows.

Search Expo Config Fields

Look up app.json and app.config.js field keys with platform coverage, requirement level, value type, and setup notes. Copy keys instantly or export filtered CSV output.

Try: bundleIdentifier, updates.url, plugins

Filtered fields

24

Required fields

5

Conditional fields

7

Expo Config Keys

Select any key to view field purpose, value format, example, and implementation notes.

RequiredCore IdentityAll
RequiredCore IdentityAll
RequiredVersioningAll
OptionalUIAll
OptionalUIAll
OptionalAssetsAll
OptionalAssetsAll
OptionalAssetsAll
OptionalAssetsAll
ConditionalRoutingiOS, Android
OptionalBuildAll
OptionalRuntimeAll
ConditionalUpdatesAll, EAS
ConditionalUpdatesAll, EAS
RequirediOSiOS
ConditionaliOSiOS
OptionaliOSiOS
RequiredAndroidAndroid
ConditionalAndroidAndroid
ConditionalAndroidAndroid
OptionalAndroidAndroid
OptionalAndroidAndroid
OptionalWebWeb
ConditionalEASEAS
Field Details

Config key

expo.name

Purpose

Display name shown on device launchers and app stores.

Value type

String

Platforms

All

Accuracy note

This Expo config reference focuses on production-relevant fields used frequently in app.json and app.config.js workflows. Always validate final values against your current Expo SDK docs and release pipeline requirements.

Why Use This Expo Config Reference?

Built for real-world Expo workflows: setup, QA, release checks, and team alignment.

Platform-aware key lookup

Filter keys by iOS, Android, Web, and EAS context so you only review fields relevant to your current task.

Requirement-level clarity

See whether fields are required, optional, or conditional to prioritize configuration work before builds and submissions.

Purpose and value-type guidance

Each field includes practical purpose, expected value type, and implementation notes to reduce trial-and-error edits.

Copy and export ready

Copy individual keys or export filtered CSV data for engineering docs, QA checklists, and release runbooks.

Common Use Cases

Where this config reference adds speed and accuracy across Expo projects.

Initial project setup

Quickly map required Expo config keys when bootstrapping new apps with iOS, Android, Web, and EAS support.

Release readiness checks

Verify versioning, package IDs, update settings, and platform-specific config fields before store submissions.

QA and build troubleshooting

Cross-check config fields during build failures, runtime mismatches, and update-channel issues across environments.

Mobile platform targeting

Filter iOS and Android fields to isolate only native values needed for signing, permissions, and build numbering.

Config governance

Keep team standards consistent with copy-ready field keys, value examples, and implementation notes.

Developer onboarding

Use the reference as a practical training resource for engineers new to Expo config conventions.

Frequently Asked Questions

Answers for common Expo config setup and release questions.

What is Expo Config Reference?+

Expo Config Reference is a searchable guide for app.json and app.config.js field keys, including platform scope, requirement level, value type, and practical setup notes.

Can I use this for both app.json and app.config.js?+

Yes. The key reference applies to both static app.json and dynamic app.config.js workflows. You can use it for quick lookup while configuring Expo projects.

Does this tool show platform-specific fields?+

Yes. You can filter fields by iOS, Android, Web, EAS, or cross-platform scope to focus only on relevant config keys.

Is this Expo config lookup free?+

Yes. The reference tool is 100% free with no signup, no account, and no usage limits.

Should I still verify values with Expo SDK docs?+

Yes. This tool is optimized for quick implementation workflows, but final release settings should always be verified against your active Expo SDK documentation and build pipeline.

Related Tools