🙈

.gitignore Generator

Compose a .gitignore from curated per-stack templates — deduped and ready to commit.

100% LOCAL12 stack templatesMerge & dedupeCopy or download100% local

Stacks & platforms

3 templates · 16 rule lines

# .gitignore — generated with FreeToolHub

node_modules/
npm-debug.log*
yarn-error.log*
.env
.env.local
coverage/
dist/
build/

.DS_Store
.AppleDouble
.LSOverride
._*

.vscode/*
!.vscode/settings.json
!.vscode/extensions.json
history/

Data Source & Legal Disclaimer

Effective: 2026Last updated: TodayUpdate: Manual review

Sources: GitHub gitignore templates

The .gitignore is generated locally from templates. Nothing is uploaded.

See all data sources & update policy →

How .gitignore patterns work — illustrated

Git matches patterns top-to-bottom: later rules can re-include earlier exclusions — that is why the VS Code template excludes .vscode/* then re-includes !.vscode/settings.json. A trailing slash (build/) restricts matches to directories; * globs within a path segment, and patterns with a slash are anchored to the repository root. Combining templates is safe because this generator dedupes identical lines across stacks — picking Node + macOS + VS Code yields one clean file, not three copies of the same rules.

Pick stacks → union of blocks (deduped) → one .gitignore

Template blocks overlap heavily; the builder keeps the first occurrence of each unique line.

A new monorepo — Dev's first commit hygiene

Dev starts a TypeScript monorepo on a Mac with teammates on Windows, all using VS Code, deploying to Cloudflare.

Pick the stacks:He checks Node, macOS, Windows, VS Code, and Cloudflare — five templates, one click each
Review the union:The output merges all five: node_modules/, .DS_Store/, Thumbs.db, .vscode/* with its two re-includes, and .wrangler/ — duplicates like node_modules/ appear once because the builder dedupes
Commit before the first push:He downloads the file into the repo root before committing anything, so node_modules never enters history
Later additions:When a Python service joins the monorepo, he regenerates with the Python template checked — existing rules stay stable, new ones append

↩ Back to generator

About this tool

What is this tool?

Generate .gitignore files online free from 12 stack templates, merged with duplicates removed.

12 stack templatesMerge & dedupeCopy or download100% local

Why Stack-Combined Ignore Files

Every real project spans several ecosystems at once: a Next.js app on Windows in VS Code needs runtime ignores, OS junk filters, and editor noise exclusion simultaneously. Instead of copying one template and hand-adding the rest, pick all that apply and get a merged, deduplicated file in one shot.

Twelve Templates, One Clean Output

The generator stacks Node, Python, Go, Rust, React, Next.js, Django, Cloudflare, macOS, Windows, VS Code, and JetBrains templates, then removes duplicate rules that overlap between them. The result is one clean .gitignore that reads like a human wrote it - because the deduplication is what a careful human would have done anyway.

Frequently Asked Questions

Which templates should I combine?

Start with your language runtime (Node, Python, Go, or Rust), add your framework if one applies (React, Next.js, Django), then add your editor (VS Code or JetBrains) and your OS (macOS or Windows). A typical web project uses four to five templates stacked together.

What does merged and deduplicated mean?

Templates overlap - Node, React, and Next.js all ignore node_modules, for example. The generator merges your selection into one file and removes duplicate rules, so you get a clean .gitignore without the repeated blocks that stacking raw templates would produce.

Do the templates cover secrets and env files?

Yes, the runtime templates include .env patterns and common credential paths. But no generator can know the specific secrets of your project - always review the output before your first commit, and never rely on .gitignore alone as your only safeguard.