Developer Tools

.gitignore Generator

Build a .gitignore from templates for languages, frameworks, editors, and operating systems, with duplicates removed.

Find a template

Languages

Frameworks

Tools

Editors & IDEs

Operating systems

Extra patterns

4 templates selected · Patterns repeated across templates are listed only once.

.gitignore

### Node.js ###
# Dependencies
node_modules/
.pnp
.pnp.js
.yarn/*
!.yarn/patches
!.yarn/plugins
!.yarn/releases

# Logs
logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*

# Build output
dist/
build/
coverage/
.cache/
*.tsbuildinfo

# Environment
.env
.env.*
!.env.example

### macOS ###
# macOS
.DS_Store
.AppleDouble
.LSOverride
._*
.Spotlight-V100
.Trashes
.fseventsd

### Windows ###
# Windows
Thumbs.db
Thumbs.db:encryptable
ehthumbs.db
Desktop.ini
$RECYCLE.BIN/
*.lnk
*.stackdump

### VS Code ###
# VS Code
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
*.code-workspace
.history/

What is this tool?

Keep build output, dependencies, secrets, and editor clutter out of your repository. Pick the languages, frameworks, tools, editors, and operating systems you use, add your own patterns, and download a tidy .gitignore with each section labelled and duplicate rules removed.

Templates are based on widely used community conventions and cover 28 languages, frameworks, tools, editors, and operating systems. Sections keep their comments so you can see why each rule is there.

A .gitignore only affects untracked files. If a file is already committed, remove it from the index with git rm --cached <file> before the rule takes effect.

How to use the .gitignore Generator

Search for or click the templates you need — for example Node.js, Next.js, VS Code, and macOS.
Add any custom patterns, one per line.
Review the combined file; patterns shared by several templates appear only once.
Download it as .gitignore and place it in the root of your repository.

Examples

Node.js essentials

node_modules/
dist/
.env
*.log

Frequently asked questions

Where should the .gitignore file go?

In the root folder of your repository. You can add more .gitignore files in subfolders; their rules apply relative to their own folder.

Why is a file still tracked after I ignored it?

Git keeps tracking files that were committed before the rule existed. Run git rm --cached <file>, commit, and the rule will apply from then on.

What does ! mean in a .gitignore?

A leading ! re-includes a file that an earlier pattern excluded, for example !.env.example to keep a sample environment file.

Should I ignore editor settings?

Ignore personal settings, but many teams commit shared files such as .vscode/extensions.json. The VS Code template keeps those shared files and ignores the rest.

Want more power later?

Premium tools, higher limits, and API access are on the roadmap. V1 stays free and private in your browser.