.gitignore Generator
Build a .gitignore for your languages, frameworks, editors and OS.
One .gitignore For Your Whole Stack
Tick everything your project touches — Node.js, Python, Java, Go, Rust, Unity, Terraform and more, the editors your team uses, and the operating systems they run — and get one merged .gitignore with each block labelled and duplicate patterns removed.
The templates cover build output, dependency folders, caches, logs and, most importantly, local secrets such as .env files and private keys, which are the files that cause real damage when committed.
Key features
- 26 templates — languages, frameworks, editors and operating systems.
- Merged and de-duplicated, with each section labelled.
- Secrets covered — .env, key files and credentials, with .env.example kept.
- Filter to find a template fast.
- Download as .gitignore, ready to drop in the repository root.
This tool runs entirely inside your browser using native Web APIs. Your files and text are never uploaded to a server, never logged and never shared with third parties.
How to use: .gitignore Generator
- Tick your stack
Language, framework, editor and OS. - Review the file
Each block is labelled with its template. - Download or copy
Save it as .gitignore in the repository root. - Untrack old files
Run git rm --cached on anything already committed.
Technical specifications
| Processing location | Entirely in your browser — no server round trip |
|---|---|
| Data uploaded | None. Files and text never leave your device |
| Price | Free — no account, no trial, no usage cap |
| Category | Developer |
| Works offline | Yes, once the page has loaded |
| Browser support | Chrome 90+, Edge 90+, Firefox 90+, Safari 15+ |
| Interface languages | English, 中文, हिन्दी, Español, العربية |
Frequently asked questions
Why is a file still tracked after adding it to .gitignore?
.gitignore only stops untracked files from being added. A file that is already committed stays tracked until you remove it from the index with git rm --cached path/to/file and commit that change.
Where does the .gitignore file go?
Usually in the root of the repository. Git also reads .gitignore files in subfolders, which apply to that folder and below.
I committed a secret — is deleting it enough?
No. It stays in the history. Rotate the secret immediately, then rewrite history with a tool such as git filter-repo if the repository is shared.
What does ! mean in a .gitignore?
It un-ignores a pattern, so .env* followed by !.env.example ignores every environment file except the example that documents which variables are needed.
Should editor folders be in the project .gitignore?
Many teams put .idea/ and .vscode/ in a personal global ignore file instead (git config --global core.excludesFile). Including them in the project file is simpler and harmless.