Pick languages, frameworks, and editors to instantly build a combined .gitignore file, in your browser.
Updated
/ 5 - Be the first to rate this tool Thanks for rating!
Verification failed - please try again.
Quick check
Please verify you're not a robot to submit your rating.
Give feedback
Tell us what you think about Generate a .gitignore file online.
- Runs entirely in your browser — nothing is sent to a server
- Combine templates for multiple languages, frameworks, and editors
- Free, no account required
How it works
-
1
Tick the stacks, systems and editors you use.
-
2
Review the generated sections.
-
3
Copy the file and save it as .gitignore in your project root.
About the .gitignore Generator
A missing .gitignore lets node_modules, vendor folders, editor settings and .env secrets slip into a repository. This generator assembles a starting .gitignore from short templates for common stacks, operating systems and editors. Tick what applies to your project and the file is built with a labelled section for each choice, ready to paste into the root of your repository.
What you can do
- Combine templates for Node, PHP / Laravel, Python, macOS, Windows, VS Code and JetBrains.
- Start from Node, macOS and VS Code, which are ticked by default.
- See each template under its own ### heading so you know where every rule came from.
- Copy the finished file in one click.
When it works best
- Starting a new repository and wanting sensible ignores before the first commit.
- Adding OS and editor rules to a project shared by people on Mac, Windows and different IDEs.
- Checking whether a Laravel or Python project already ignores its cache and environment files.
Things to know
- The file is assembled in your browser.
- Templates are deliberately short and cover common files only, so add rules for your build output, logs or tools.
- Every stack template ignores .env. Commit a .env.example instead if teammates need to know which variables exist.
- A .gitignore does not remove files Git already tracks; run git rm --cached on them first.
Frequently asked questions
Node, PHP / Laravel, Python, macOS, Windows, VS Code and JetBrains.
Yes, by every stack template. Commit a .env.example instead.
A .gitignore does not untrack files. Run git rm --cached on them first.
They cover common files only, so add rules for your build output and logs.