.gitignore for Xcode

Xcode build artifacts, user-specific workspace data, and DerivedData.

Quick presets

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

21 patterns · 418 B

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

# ---- Xcode ----
# Xcode
build/
DerivedData/
*.pbxuser
!default.pbxuser
*.mode1v3
!default.mode1v3
*.mode2v3
!default.mode2v3
*.perspectivev3
!default.perspectivev3
xcuserdata/
*.moved-aside
*.xccheckout
*.xcscmblueprint
*.hmap
*.ipa
*.dSYM.zip
*.dSYM
timeline.xctimeline
playground.xcworkspace
.build/

What this template ignores

Ignores Xcode build output (DerivedData, build/), user-specific workspace data (xcuserdata/), compiled .ipa files, and debug symbol archives.

Common additions

  • +Pods/ — if using CocoaPods and not committing dependencies
  • +.swiftpm/ — Swift Package Manager build artifacts

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 Pods/ or Package.resolved?
Package.resolved should be committed (locks dependency versions). Pods/ is debated — committing it speeds up CI but increases repo size.

Looking for something else? Browse all templates →