.gitignore generator
Combine official GitHub gitignore templates and download a .gitignore.
Runs in this tab. The file stays here.
Loading templates…
Select templates in the side panel.
This runs in your browser. Nothing is uploaded.
About .gitignore generator
Combine official GitHub gitignore templates in your browser and download a .gitignore. Templates ship with the site, so wifi-off still works after load.
Starting a repo should not mean hunting Stack Overflow for the Node template again. This page loads a baked snapshot of GitHub’s gitignore collection, lets you multi-select stacks, and concatenates them with clear section headers. Add custom patterns in a free-text box and download a ready .gitignore.
Templates are baked at build time on purpose. Fetching GitHub on every visit would break the offline promise and add a live dependency. Re-bake periodically when you want upstream updates. Until then, the committed JSON is the source of truth in production.
I do not invent ignore rules for proprietary tools you never selected. If a path still shows up in git status, add it under custom patterns.
Edge cases include overlapping templates that both ignore node_modules, monorepos where the git root is not the package root, and secrets that no template knows about. A gitignore only affects untracked files; already-committed keys need git rm --cached, not a longer ignore file. Global gitignore on your machine is separate from what this page generates.
Your selections and custom lines never leave the tab. There is no “save my stack profile” server. Download or copy the file when you are happy. On a plane after the page has loaded, search and combine still work because the template JSON shipped with the static site.
How to use .gitignore generator
- 1Search and select one or more templates from the list.
- 2Optionally paste extra patterns into the custom box.
- 3Copy the result or download it as .gitignore.
What it won't do
- Templates are a snapshot, not live GitHub.
- Does not edit .git/info/exclude or global gitignore on your machine.
Common questions
Are templates fetched from GitHub when I click?
No. They were baked into a static JSON file when the site was built. Your session does not call GitHub.
Can I mix Node, macOS, and VisualStudioCode?
Yes. Selections concatenate with named headers between sections.
Will this remove files already tracked by git?
No. A gitignore only affects untracked paths. Use git rm --cached for mistakes already committed.
How stale can baked templates get?
They reflect whatever was baked at site build time. New upstream templates appear here only after a rebuild and redeploy, not on every page visit.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation