gitignore Generator
Build a .gitignore file for your languages and tools, so junk files stay out of version control.
Keeping the clutter out of Git
A .gitignore file tells Git which files to leave untracked — the build output, dependency folders, editor settings, logs and secrets that should never be committed. This assembles a .gitignore from the languages, frameworks and tools you use, combining the well-established patterns for each so you do not have to remember them or write them from scratch.
Choose your stack and the combined .gitignore is generated.
What you really don't want committed
Getting this right early prevents two headaches. The first is bloat: commit a dependency folder or build artifacts and your repository balloons with files that should be regenerated, not stored. The second, more serious, is secrets: an environment file with API keys or passwords committed to a repo, especially a public one, is a genuine security incident. A good .gitignore excludes those by default, which is why starting from proven patterns for your stack beats hand-writing one and missing something important.
Frequently asked questions
What should a .gitignore exclude?
Build output, dependency folders, editor and OS files, logs, and above all secrets like environment files with keys.
Why does it matter for security?
Committing an environment file with API keys, especially to a public repo, is a real security incident. A good .gitignore prevents it.
Is anything uploaded?
No. The file is generated in your browser.