.gitignore Generator

Pick the languages, frameworks, operating systems and editors your project uses and get a combined .gitignore with curated rules. Everything runs in your browser — nothing is sent anywhere and nothing is stored.

No items selected

How to use the .gitignore generator

  1. Search or scroll the list and tick every technology your project uses — languages, frameworks, your operating system and your editor.
  2. The combined .gitignore builds instantly on the right, with each group under a clear ### Section header.
  3. Click Copy to put it on your clipboard, or Download to save a ready-to-commit .gitignore file.

Place the file at the root of your repository and commit it so your whole team ignores the same build output, dependencies, logs and editor files. Remember that ignore rules only apply to untracked files — use git rm --cached <file> for something already committed.

More PAYATE tools

Word CounterCount words, characters & more Lorem IpsumPlaceholder text for mockups Compound InterestSavings growth & interest Random PickerWheel, dice, coin & list

Frequently asked questions

What is a .gitignore file?

A .gitignore file tells Git which files and folders to leave untracked — build output, dependencies, logs, editor settings and OS junk. Git skips anything matching a pattern in it, so those files never get committed. It lives at the root of your repository (you can also have one per folder).

How does this generator work?

Pick the languages, frameworks, operating systems and editors your project uses from the list. The tool stitches together a curated block of rules for each selection, each under a clear ### Section header, into one combined .gitignore you can copy or download. Everything happens in your browser — nothing is uploaded or stored.

Should I commit the .gitignore file itself?

Yes. The .gitignore file is meant to be committed and shared with your team so everyone ignores the same files. Place it at the repository root and commit it like any other source file.

It is not ignoring a file I already committed — why?

A .gitignore rule only affects untracked files. If a file was already committed, Git keeps tracking it. Remove it from tracking with git rm --cached <file> (it stays on disk) and then commit — after that the ignore rule applies.

Can I combine several technologies?

Yes — that is the point. Select as many as you need (for example Node, Python, VS Code, macOS and Windows) and the rules are merged into a single file with each group clearly labelled, so a mixed-stack project is covered by one .gitignore.

Are my selections or data sent anywhere?

No. The rule blocks are embedded in the page and the file is assembled entirely client-side in JavaScript. Nothing about your project, selections or output is sent to a server, and nothing is stored.