.gitignore for Next.js

Next.js build output, cache, and environment files.

Quick presets

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

9 patterns · 255 B

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

# ---- Next.js ----
# Next.js
.next/
out/
build/
node_modules/
.env*.local
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*

What this template ignores

Ignores the .next/ build cache and output directory, static export out/, and local .env overrides.

Common additions

  • +.env.local — local secrets (never commit)
  • +.vercel — Vercel deployment cache

Commonly paired with

nodereacttypescriptvercelCombine →

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.
Why is .next/ ignored?
.next/ contains compiled pages, chunks, and build manifests. It is regenerated by next build and should never be committed.

Looking for something else? Browse all templates →