.gitignore Generator

Generate a .gitignore file with presets for Node.js, Python, Docker, IDEs, and operating systems.

For this tool, processing runs locally in your browser and data is not sent to the server.

Gitignore Generator is a free online tool that builds a .gitignore file from presets for Node.js, Next.js, Python, Django, Docker, VS Code, Cursor, JetBrains, macOS, Windows, Linux, and .env files. You can add custom rules and download the finished file. The tool runs in your browser and does not send data to the server.

What it does

Output

Processing

Continue working

Choose a related tool for the next step.

Data passed between tools is kept only in the current browser session.

How to use

Select presets for your project stack: Node.js, Next.js, Python, Django, Docker, IDEs, operating systems, and .env files.
Add any custom rules in the additional rules field.
Generate the .gitignore and review warnings about .env, lock files, and already-tracked files.
Copy or download the .gitignore and place it in the root of your repository.

More about this tool

Gitignore Generator helps you quickly build a .gitignore file for your project. You can choose presets for Node.js, Next.js, Python, Django, Docker, VS Code, Cursor, JetBrains, macOS, Windows, Linux, .env files, and secret keys. The tool adds typical rules for build and cache artifacts, dependencies, temporary files, IDEs, and secrets.

.gitignore affects only newly untracked files. It does not remove files that have already been committed to the repository. To stop tracking a previously committed file, use git rm --cached followed by a commit.

All processing is done locally in the browser. Your data is not sent to the server.

Runs in the browser
Data is not sent to the server
Generates .gitignore from presets
Supports Node.js, Next.js, Python, and Django
Includes rules for Docker, IDEs, and operating systems
Adds .env and secret key patterns
Supports custom rules
Can download the finished .gitignore
No registration required

Frequently Asked Questions

What is .gitignore?

.gitignore is a file with rules that tell Git which newly untracked files and directories should not be added to the repository.

Where should .gitignore be placed?

.gitignore is typically placed in the repository root, alongside package.json, pyproject.toml, manage.py, or other project files.

Will .gitignore remove already-committed files?

No. .gitignore does not remove files that Git is already tracking. For those files, use git rm --cached and then commit the change.

Should node_modules be ignored?

Yes. node_modules is typically not committed because dependencies are restored via npm, yarn, or pnpm.

Should lock files be ignored?

Lock files such as package-lock.json, yarn.lock, pnpm-lock.yaml, or poetry.lock are usually committed for reproducible builds. Ignoring them should be a deliberate project decision.

Should .env be added to .gitignore?

Yes. Real .env files often contain tokens, passwords, connection strings, and private keys. Commit .env.example without real secrets instead.

Can I add rules for VS Code or Cursor?

Yes. You can add IDE rules. Note that .cursor/rules/ is best not ignored by default if project rules should be stored in the repository.

Can I download the finished .gitignore?

Yes. The tool lets you copy the result or download it as a file named .gitignore.

Is my data sent to the server?

No. The .gitignore file is generated locally in the browser and is not sent to the server.

Do I need to register?

No. The tool works immediately without registration.

How to use

Select presets for your project stack: Node.js, Next.js, Python, Django, Docker, IDEs, operating systems, and .env files.

Add any custom rules in the additional rules field.

Generate the .gitignore and review warnings about .env, lock files, and already-tracked files.

Copy or download the .gitignore and place it in the root of your repository.

More about this tool

All processing is done locally in the browser. Your data is not sent to the server.

Runs in the browser
Data is not sent to the server
Generates .gitignore from presets
Supports Node.js, Next.js, Python, and Django
Includes rules for Docker, IDEs, and operating systems
Adds .env and secret key patterns
Supports custom rules
Can download the finished .gitignore
No registration required

Frequently Asked Questions

What is .gitignore?

.gitignore is a file with rules that tell Git which newly untracked files and directories should not be added to the repository.

Where should .gitignore be placed?

.gitignore is typically placed in the repository root, alongside package.json, pyproject.toml, manage.py, or other project files.

Will .gitignore remove already-committed files?

No. .gitignore does not remove files that Git is already tracking. For those files, use git rm --cached and then commit the change.

Should node_modules be ignored?

Yes. node_modules is typically not committed because dependencies are restored via npm, yarn, or pnpm.

Should lock files be ignored?

Lock files such as package-lock.json, yarn.lock, pnpm-lock.yaml, or poetry.lock are usually committed for reproducible builds. Ignoring them should be a deliberate project decision.

Should .env be added to .gitignore?

Yes. Real .env files often contain tokens, passwords, connection strings, and private keys. Commit .env.example without real secrets instead.

Can I add rules for VS Code or Cursor?

Yes. You can add IDE rules. Note that .cursor/rules/ is best not ignored by default if project rules should be stored in the repository.

Can I download the finished .gitignore?

Yes. The tool lets you copy the result or download it as a file named .gitignore.

Is my data sent to the server?

No. The .gitignore file is generated locally in the browser and is not sent to the server.

Do I need to register?

No. The tool works immediately without registration.