Which technologies does the generator cover?

There are presets for Node.js, Python, Python venv, React, Next.js, Java, Go, Rust, and Ruby, plus operating system noise for macOS, Windows, and Linux, editor files for VS Code and JetBrains, and a dedicated .env files group. You can combine any number of them in a single file.

How are duplicate patterns handled when I select several presets?

The tool tracks every line it has already written and skips exact repeats. So if both the Node.js and React presets include node_modules/, it appears only once in the final file. Each preset's remaining unique lines are grouped under a labeled comment header.

Can I download the file directly as .gitignore?

Yes. Besides copying to the clipboard, there is a Download .gitignore button that creates the file in the browser and saves it with the correct dotfile name. Because the leading dot can be hidden by your operating system, you may need to enable hidden files to see it after downloading.

Does the tool detect my project's stack automatically?

No. It does not read your repository or any files. You select the presets that match your project, and the tool assembles the patterns from its built-in lists. This is also why nothing about your code ever leaves your machine.

What happens if I select no presets?

The output is empty and the tool shows a prompt to select at least one preset. As soon as you tick a box, the corresponding patterns appear and the file rebuilds live as you add or remove presets.

Can I edit the generated file afterward?

Yes, and you often should. The presets cover common cases, but a niche framework or a project-specific build folder may need a line you add by hand. Treat the generated output as a solid starting point that you refine in your editor.

Why are macOS and Node.js selected by default?

They represent the most common starting configuration for a JavaScript project on a Mac, so the tool gives you a useful file immediately. You can untick them and choose any other combination at any time.

Is anything sent to a server?

No. The file is built entirely in your browser from the embedded preset lists, with no upload or network request involved.

Developer Tools

.gitignore Generator — Build Your Ignore File From Presets

🔒 Runs in your browser

Select the technologies in your project and get a clean, deduplicated .gitignore file. Covers Node, Python, React, Next.js, Java, Go, Rust, macOS, Windows, VS Code, JetBrains, and more. Copy or download in one click — no account, no upload.

How to use this tool

Select the technologies and tools used in your project.
Get a clean, deduplicated .gitignore file instantly.
Copy or download the file and add it to your repository.

About .gitignore Generator

The .gitignore Generator builds a Git ignore file from a set of technology presets, so you do not have to remember which build artifacts, dependency folders, and editor files each ecosystem leaves behind. You tick the presets that match your project and the tool assembles the corresponding patterns into a ready-to-use file. By default Node.js and macOS are pre-selected, which covers the most common starting point for a JavaScript project on a Mac.

Each preset is a curated list of glob patterns maintained inside the tool. Node.js contributes entries like node_modules/, the various debug logs, and .env files; Python adds __pycache__/, *.py[cod], and virtual environment folders; Next.js adds .next/, out/, and .vercel; and there are presets for React, Java, Go, Rust, Ruby, Windows, Linux, VS Code, JetBrains, and a dedicated .env files group. When you select more than one preset the tool concatenates them under labeled comment headers (for example, # Node.js) and runs a deduplication pass: a Set tracks every line that has already been emitted, so a pattern shared by two presets, such as node_modules/ appearing in both Node and React, is written only once. The output updates live as you toggle presets.

Typical uses are scaffolding a new repository, standardizing ignore rules across a polyglot monorepo, or quickly adding OS and editor noise patterns to an existing project. You can copy the result to the clipboard or download it directly as a file named .gitignore via an in-browser Blob and object URL, with no upload step. Everything is generated locally in your browser from the embedded preset lists, so nothing about your project is transmitted.

A few limitations are worth knowing. The preset catalog is fixed, so very niche frameworks may not have a dedicated entry and you may need to add a line or two by hand afterward. Deduplication matches lines exactly, so two patterns that achieve the same effect but are written differently (for instance build/ versus /build) are both kept. The tool also does not read your repository, so it cannot detect which technologies you actually use; you choose the presets yourself.

Frequently Asked Questions

Which technologies does the generator cover?: There are presets for Node.js, Python, Python venv, React, Next.js, Java, Go, Rust, and Ruby, plus operating system noise for macOS, Windows, and Linux, editor files for VS Code and JetBrains, and a dedicated .env files group. You can combine any number of them in a single file.
How are duplicate patterns handled when I select several presets?: The tool tracks every line it has already written and skips exact repeats. So if both the Node.js and React presets include node_modules/, it appears only once in the final file. Each preset's remaining unique lines are grouped under a labeled comment header.
Can I download the file directly as .gitignore?: Yes. Besides copying to the clipboard, there is a Download .gitignore button that creates the file in the browser and saves it with the correct dotfile name. Because the leading dot can be hidden by your operating system, you may need to enable hidden files to see it after downloading.
Does the tool detect my project's stack automatically?: No. It does not read your repository or any files. You select the presets that match your project, and the tool assembles the patterns from its built-in lists. This is also why nothing about your code ever leaves your machine.
What happens if I select no presets?: The output is empty and the tool shows a prompt to select at least one preset. As soon as you tick a box, the corresponding patterns appear and the file rebuilds live as you add or remove presets.
Can I edit the generated file afterward?: Yes, and you often should. The presets cover common cases, but a niche framework or a project-specific build folder may need a line you add by hand. Treat the generated output as a solid starting point that you refine in your editor.
Why are macOS and Node.js selected by default?: They represent the most common starting configuration for a JavaScript project on a Mac, so the tool gives you a useful file immediately. You can untick them and choose any other combination at any time.
Is anything sent to a server?: No. The file is built entirely in your browser from the embedded preset lists, with no upload or network request involved.