.gitignore Generator
Combine ignore templates for your stack and tools.
# Node
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
pnpm-debug.log*
.npm
.pnp.*
dist/
build/
coverage/
.env
.env.local
.cache/
# macOS
.DS_Store
.AppleDouble
.LSOverride
Icon
._*
.Spotlight-V100
.Trashes
.fseventsdHow to use
- 1 Tick each language, OS or editor your project uses.
- 2 Watch the combined .gitignore build in real time.
- 3 Review the labelled, de-duplicated sections.
- 4 Copy the file and save it as .gitignore in your repo root.
About .gitignore Generator
The .gitignore Generator assembles a ready-to-commit ignore file from curated templates for the languages, operating systems and editors you actually use.
Tick the stacks you need — Node, Python, Java, Rust, Go and others — alongside the noise your machine and tools create, such as macOS .DS_Store files, Windows Thumbs.db, Visual Studio Code settings and JetBrains .idea folders.
The combined file appears instantly, grouped into clearly labelled sections.
A good .gitignore stops you from committing dependencies, build output, environment files and editor cruft, and it is one of the first things a new repository needs.
Hand-copying snippets from different sources tends to produce duplicate patterns and a messy file; this generator merges everything for you and removes any pattern that would otherwise appear twice, so the result stays clean no matter how many stacks you combine.
Sections always come out in a stable order, which keeps diffs small when you add a stack later.
It is the fastest way to bootstrap the ignore file for a fresh project or to add a missing language or tool to an existing one.
The templates cover the patterns that matter most for each stack rather than trying to be exhaustive, so the output stays readable.
Everything is generated in your browser with no network calls, and the copy button gives you the whole file in one click.
FAQ
Which stacks are included?
Node, Python, Java, Rust, Go, macOS, Windows, Linux, Visual Studio Code and JetBrains, covering the most common language, OS and editor combinations.
What happens to duplicate patterns?
Identical patterns that appear in more than one template are written only once, so combining several stacks never produces a repeated line.