UtilityKit

500+ fast, free tools. Most run in your browser only; Image & PDF tools upload files to the backend when you run them.

Gitignore Generator

Generate merged and deduplicated .gitignore output from stack presets.

About Gitignore Generator

Accidentally committing build artifacts, node_modules, or IDE config files to your repository is a rite of passage for most developers — and a persistent headache once it happens. Cleaning up a polluted git history is painful, which is why getting your .gitignore right from project day one matters. The .gitignore Generator lets you select one or more languages, frameworks, and tools — Node.js, Python, Go, React, JetBrains IDEs, macOS, Docker, and dozens more — and instantly produces a clean, comprehensive .gitignore file you can drop straight into your project root. Instead of hunting through GitHub gitignore collection or copying from old projects, you get a merged, deduplicated file built from community-maintained templates.

Why use Gitignore Generator

Prevents Accidental Secret Commits

Entries for .env files, credential configs, and key stores are included by default for relevant stacks, creating a safety net that stops sensitive data from reaching public or shared repositories before you realise the mistake.

Merges Multiple Stacks Into One File

Full-stack projects typically span two or three environments. The generator deduplicates and merges entries from Node, Python, Docker, and any IDE you select into a single coherent file instead of you manually concatenating templates.

Based on Community-Maintained Templates

Output is derived from the same curated templates used by millions of open source projects, so you get battle-tested patterns rather than a hastily written list that misses obscure build directories.

Keeps Repositories Lean and Fast

Excluding node_modules, __pycache__, .gradle, and other heavy directories from tracking prevents your repository from ballooning in size, keeps clone times fast, and reduces storage costs on hosted platforms.

Eliminates Noisy Diffs From Editor Files

IDE workspace files and OS-generated metadata like .DS_Store or Thumbs.db constantly change but carry no semantic value. Ignoring them from the start means every diff and pull request review stays focused on real code changes.

Instant Results Without Template Hunting

No need to browse GitHub's gitignore repository, cross-reference multiple files, or remember which directories each build tool uses. The generator handles the research so you can move on to writing actual code.

How to use Gitignore Generator

Select one or more languages or frameworks your project uses from the picker
Add any IDE or tooling entries such as JetBrains, VSCode, or macOS to the selection
Click Generate to produce a merged, deduplicated .gitignore file
Review the output and optionally remove sections irrelevant to your project
Click Copy to copy the full file content to your clipboard
Paste the content into a .gitignore file in your project root and commit it

When to use Gitignore Generator

When initialising a new project and you need a .gitignore before your first commit
When adding a new language or framework to an existing monorepo
When onboarding a team member who asked why IDE files keep appearing in pull requests
When migrating a project from one stack to another and the old .gitignore no longer fits
When you inherited a repository with no .gitignore and need to retroactively clean it up
When contributing to an open source project that requires a .gitignore update in your pull request

Examples

Node.js + macOS

Input: Languages: Node.js, macOS

Output: node_modules/ npm-debug.log* yarn-debug.log* yarn-error.log* .env .env.local .env.*.local dist/ build/ .DS_Store .AppleDouble .LSOverride ._* .Spotlight-V100 .Trashes

Python + JetBrains IDE

Input: Languages: Python, JetBrains IDEs

Output: __pycache__/ *.py[cod] *$py.class *.egg-info/ dist/ build/ .venv/ venv/ .env .idea/ *.iml *.iws *.ipr out/

Go + Docker

Input: Languages: Go, Docker

Output: # Go build/ *.exe *.exe~ *.dll *.so *.dylib vendor/ # Docker .dockerignore docker-compose.override.yml *.env .env

Tips

Add OS-specific entries like macOS or Windows even if your team is mixed — it prevents contributors from accidentally pushing .DS_Store or Thumbs.db files regardless of their machine
Place your most project-specific ignores at the bottom of the generated file with a comment block so they are easy to find and update later
If node_modules or a similar heavy directory is already tracked, run git rm -r --cached node_modules and re-commit to stop tracking it without deleting it from disk
Use the ! negation prefix to un-ignore a specific file inside an ignored directory, such as !dist/.gitkeep to preserve an empty placeholder folder
Commit your .gitignore as the very first or second commit in a project, ideally before any other files are added, to avoid having to retroactively untrack accidentally staged files

Frequently Asked Questions

Can I select multiple languages and frameworks at once?▾

Yes. You can select any combination of stacks, such as Node.js, React, and Docker together. The generator merges all selected templates and removes duplicate entries so the output is a single clean file.

Will the generator cover my IDE-specific files?▾

Entries for JetBrains IDEs (IntelliJ, WebStorm, PyCharm), Visual Studio Code, Vim, Emacs, and Sublime Text are all available as standalone selections. Add any that apply to your team's setup.

Does the generated file ignore .env files?▾

Yes, for stacks where environment files are common such as Node.js and Python, the generated output includes entries for .env, .env.local, .env.*.local, and similar patterns. Always verify these entries are present before your first push.

What if I need to ignore a custom directory not covered by the templates?▾

After generating and copying the file, manually append entries for project-specific paths at the bottom. Lines starting with # are comments. Standard glob patterns like /dist/ or *.log work as expected.

How does a .gitignore differ from a .gitignore_global file?▾

A per-repository .gitignore applies only to that project and should be committed so all contributors benefit from it. A .gitignore_global lives in your home directory and applies to every repository on your machine, making it suitable for personal IDE or OS entries.

Will adding .gitignore untrack files already committed?▾

No. Once a file is tracked by git, a .gitignore entry alone will not stop git from watching it. You must run git rm --cached <file> to untrack it, then commit the removal alongside your updated .gitignore.

Is the output compatible with GitHub, GitLab, and Bitbucket?▾

Yes. The .gitignore format is a git standard and works identically across all hosting platforms. There are no platform-specific syntax differences.

Can I use the generated file as a starting point and edit it afterward?▾

Absolutely, and that is the intended workflow. The generator provides a comprehensive baseline. You should then review the output and remove any sections that do not apply to your specific project structure.

Explore the category

Glossary

.gitignore: A plain-text file placed in a git repository directory that tells git which files and directories to leave untracked. Patterns support wildcards and directory-relative paths.
Glob pattern: A string using wildcard characters such as * (any characters) and ** (any path depth) to match groups of filenames. Git uses glob syntax to evaluate .gitignore rules.
Tracked file: A file that git already knows about because it was previously staged and committed. A .gitignore entry does not affect files that are already tracked.
git rm --cached: A git command that removes a file from git's index (stops tracking it) without deleting the file from your working directory. Used to untrack files that should be ignored.
Negation pattern: A .gitignore line starting with ! that re-includes a file or directory that would otherwise match an earlier ignore rule. Useful for keeping specific files inside ignored folders.
.gitignore_global: A user-level gitignore file configured via git config --global core.excludesfile that applies to every repository on the machine, typically used for personal editor or OS-specific ignores.