Gitignore Generator
Generate .gitignore files for various platforms, languages, and frameworks
About this ToolHow it works, benefits & use casesTap to collapse
Build a .gitignore by ticking the templates that match your stack instead of hunting for the right patterns to ignore. The generator ships a curated set of templates grouped into Languages (Node.js, Python, Java, Go, Rust, PHP), Frameworks (React, Next.js), operating systems (macOS, Windows, Linux), and IDEs (VS Code, JetBrains). Filter by category tab or type in the search box to find a template by name, then check as many as you need — the combined .gitignore updates live below, each section prefixed with a comment header so you can see where Node.js rules end and macOS rules begin. Selections persist locally so your choices survive a refresh, and the running count tells you how many templates are active. When the file looks right, copy it or download it as .gitignore straight into your repository root. It all runs in your browser with no account required.
How to Use
- 1Filter the template list with the category tabs (Languages, Frameworks, OS, IDEs) or type a name into the search box.
- 2Tick the checkbox on each template that matches your project — for example Node.js, VS Code, and macOS.
- 3Watch the Generated .gitignore panel update live as you combine templates, each with its own comment header.
- 4Use Select visible to add every template in the current filter, or Clear all to start over.
- 5Copy or download the result and place it as .gitignore in the root of your Git repository.
Key Benefits
- Curated templates for languages, frameworks, operating systems, and IDEs
- Combine multiple templates into one file with labelled comment sections
- Live preview that rebuilds the moment you check or uncheck a template
- Category tabs and a name search to find the right template fast
- Selections persist in your browser, surviving a page refresh
- Running selected-count and one-click Select visible / Clear all controls
- Copy or download directly as a .gitignore file
Common Use Cases
- Bootstrapping a fresh repository with the right ignores before the first commit
- Combining a language, framework, OS, and editor template for a polyglot project
- Adding editor or OS junk (.DS_Store, .vscode/, .idea/) to an existing .gitignore
- Standardising what teammates ignore across multiple repositories
- Quickly recalling the conventional ignore patterns for an unfamiliar stack
Filter templates
Available templates (13)
Select templates above to generate your .gitignore
# .gitignore
How to use
- Select one or more templates that match your project requirements.
- The .gitignore file updates live as you select templates.
- Download and place it in the root of your Git repository.
- You can combine multiple templates — e.g. Node.js + VS Code + macOS.
Was this tool helpful?
Share Your Experience
Help others discover this tool!
Related tools
- Component Name GeneratorTurn a description into ranked, kind-aware component names with a file scaffold and a name validator (casing, collisions, clarity)
- Heroku Procfile GeneratorBuild a Heroku Procfile and matching app.json — process types, env vars, addons, dyno formation — plus a Procfile parser and audit
- Markdown TOC GeneratorGenerate table of contents for Markdown
- Package.json Scripts GeneratorGenerate common npm scripts for different project types and workflows
- Tailwind Config GeneratorVisually build a Tailwind config - theme extend, colors, spacing, fonts, screens, plugins - and export it as a v3 JS config or a v4 @theme CSS block
- App Icon GeneratorTurn one image into complete icon sets for iOS, Android, Web/PWA & macOS — Contents.json, adaptive icons, maskable, manifest & favicon.ico — in one ZIP
The current set covers languages (Node.js, Python, Java, Go, Rust, PHP), frameworks (React, Next.js), operating systems (macOS, Windows, Linux), and IDEs (VS Code and JetBrains products like IntelliJ, WebStorm, and PyCharm). Use the category tabs or the search box to find them quickly.
Yes — that is the main workflow. Tick as many templates as you need and they are concatenated into a single .gitignore, each preceded by a comment header naming the template (for example "# Node.js" then "# macOS") so the output stays organised and easy to scan.