Skip to main content

We earn commissions, at no additional cost to you, when you shop through the links below. Learn more

DevBench
git

Gitignore Generator

DevOffline-ready

Gitignore Generator produces merged .gitignore files from 20+ language, framework, editor, and OS templates — Node.js, Python, Go, Rust, macOS, VS Code, JetBrains, and more. Select multiple templates, deduplicate entries, and copy or download a ready-to-commit .gitignore for your repository.

Related: License.env.env

Your files and inputs stay in your browser — nothing is uploaded or stored.

Languages / Runtimes

Frameworks

Editors / IDEs

OS

Tools

Output

Recommended for developers

These are affiliate links: we earn commissions, at no additional cost to you, when you shop through the links below.

How to generate a .gitignore file

  1. Tick the templates that match your project — every checkbox appends its section to the output immediately.
  2. Read the combined result below, with one commented heading per template so it stays readable in the repo.
  3. Press Copy or Download as .gitignore and drop it at the repository root.

What is inside

Five groups cover the usual suspects. Languages and runtimes: Node.js, Python, Java, Go, Rust, Ruby, PHP, C/C++, Swift and Kotlin — virtualenvs,node_modules/, build outputs and debug logs. Frameworks: React, Next.js, Vue, Angular, Django, Laravel and Spring. Editors: VS Code, JetBrains IDEs, Vim/Neovim and Eclipse, so personal workspace files never land in a shared repo. Operating systems: macOS, Windows and Linux. Tools: Docker, Terraform and Vagrant.

Combine, then review

Real projects stack patterns — a Next.js app on a Mac might tick Node.js, Next.js, VS Code and macOS at once, and the output merges them without duplicate blocks. Before the first commit, skim the result: no template list can know your custom build directory or a one-off data folder, and those are added by hand underneath the generated sections. The templates deliberately err towards including too much — dependencies, build output, caches and logs are safe to ignore, and a missing ignore rule is what actually pollutes a commit history. Because the output is plain gitignore syntax, the same file can be copied into any new repository as a starting point. The generator itself runs entirely in the browser; the templates are embedded, so it works offline and nothing is sent anywhere.

Also useful: License Generator, and .env Validator.