Gitignore Generator

Create a .gitignore file from common templates for languages, IDEs and operating systems, plus your own lines. Reorder or remove groups, merge duplicate patterns automatically and copy or download the result.

Developer Runs client-side Free to use

Jump to the tool

About the Gitignore Generator

Gitignore Generator builds a .gitignore file from templates for Node.js, Python, PHP, Java, .NET, Ruby, Go, Rust, Android, iOS/Xcode, Visual Studio Code, JetBrains IDEs, macOS, Windows and Linux. Select the ones your project needs, reorder or remove them, and add your own lines; each template appears as a labelled group with short comments explaining its patterns.

When several templates contain the same pattern, it is kept only where it first appears and later duplicates are removed, with a count shown. Comments stay with their patterns, and a comment block is dropped only if all of its patterns were duplicates. Custom lines are added as plain text, never run. The templates are common starting points rather than a complete or authoritative list, so review the result for your repository. Remember that .gitignore does not untrack files already committed.

How to use

Tick the templates for your languages, tools and operating systems.
Reorder or remove groups in the selected list.
Add any custom patterns or comments.
Review the generated .gitignore and the duplicate count.
Copy it or download it as .gitignore.

Key features

15 common templates for languages, IDEs and operating systems.
Selected groups can be reordered or removed.
Custom lines added as plain text.
Duplicate patterns merged, first occurrence kept.
Readable labelled sections with comments.
Copy .gitignore and Download .gitignore.
Works offline; nothing is stored.

Best practices

Commit .gitignore early, before adding build output or dependencies.
Keep example config files (such as .env.example) tracked.
Use git rm --cached to untrack files that are already committed.
Check order when using ! negation patterns, as later lines override earlier ones.
Never rely on .gitignore alone to keep secrets out of a repository.

Benefits

A sensible starting .gitignore in seconds.
No duplicated patterns when combining stacks.
Clear, commented sections that are easy to edit.
Private: runs entirely in your browser.

Frequently asked questions

Will .gitignore remove files already in my repository?

No. It only affects untracked files. To stop tracking a file that is already committed, run git rm --cached <file> and commit the change.

How are duplicate patterns handled?

A pattern is kept the first time it appears in the output order and removed from later groups. Comments stay; a comment block is removed only when all of its patterns were duplicates.

Can removing duplicates change behaviour?

Usually not, but .gitignore is read in order, so if you rely on a ! negation followed by the same pattern again, review the order after merging.

Are the templates complete?

No. They cover common files for each stack but are not exhaustive or suitable for every repository or security policy. Add project-specific lines and review the result.

Why did my download save as “gitignore”?

Some browsers or systems hide or rename files that start with a dot. Rename the file to .gitignore and place it in the root of your repository.

What can I put in custom lines?

Any .gitignore patterns or # comments, up to 500 lines. They are added as plain text after the templates; control characters are rejected.

Is anything I paste uploaded or saved?

No. Everything is processed in your browser on your device. Nothing is uploaded, no request is sent, and inputs and results are not saved in browser storage. Reset clears them from the page.