.gitignore for Expo

Expo React Native build artifacts, .expo directory, and native build outputs.

Quick presets

Selected (1)
Expo
Your selections never leave your browser. Generation happens entirely client-side.
Raw

8 patterns · 209 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Expo
# 2026-04-20

# ---- Expo ----
# Expo
node_modules/
.expo/
dist/
web-build/
ios/
android/
*.orig.*
.env.local

What this template ignores

Ignores .expo/ local project settings, Expo web-build/ and dist/ output, and native ios/android directories for managed workflow projects.

Common additions

  • +!ios/ — keep if using bare workflow
  • +!android/ — keep if using bare workflow

Commonly paired with

Frequently asked questions

Do I need to commit .gitignore?
Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?
Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?
Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Should I commit ios/ and android/ in Expo?
In the managed workflow: no — Expo generates them. In the bare workflow: yes — you manage them directly and they must be committed.

Looking for something else? Browse all templates →