Gitignore and Dockerignore generator
📦 Pick your stacks and copy merged starter ignore files: .gitignore, .dockerignore, .npmignore, .eslintignore, .prettierignore, or .cursorignore. Free and instant in your browser.
Tells Git which files and folders not to track.
Frequently asked questions
What is the difference between .gitignore and .dockerignore?
.gitignore tells Git which files not to track. .dockerignore tells Docker which files to exclude when sending the build context to the daemon. They use similar pattern syntax but apply to different tools; you often want both.
What is .npmignore and how is it different from .gitignore?
.npmignore controls what is included in an npm package when you run npm publish. If you do not have a .npmignore file, npm uses your .gitignore instead. You can use .npmignore to exclude tests and dev files that you still want in Git.
What are .eslintignore and .prettierignore for?
.eslintignore lists paths ESLint should skip. .prettierignore lists paths Prettier should not format. Both use a gitignore-style pattern syntax in each line.
What is .cursorignore?
.cursorignore tells the Cursor editor which files to exclude from AI indexing and features, using gitignore-style patterns. It helps avoid sending large folders like node_modules to the model.
How does multi-stack merge work?
If you select several stacks (for example Node and Python), patterns are combined in a stable order: OS and editors first, then the rest alphabetically by stack. Duplicate lines are removed while keeping the first occurrence.
Should I replace my existing ignore file with this output?
Treat this as a starter template. Review and merge with your team conventions, CI paths, and secrets rules before committing. You can paste lines into an existing file instead of replacing it entirely.
Is my data sent to a server?
No. Generation runs entirely in your browser. Nothing is uploaded.
Gitignore and Dockerignore generator
Generate a starter .gitignore, .dockerignore, .npmignore, .eslintignore, .prettierignore, or .cursorignore by selecting one or more stacks (for example Node, Python, or Go). Patterns are merged and deduplicated so you get a single file you can paste into a new repo, package publish, or editor config. No sign-up required.
Use cases
- New projects – Bootstrap ignore rules before the first commit.
- Docker builds – Reduce image context size by excluding dependencies and VCS metadata.
- Polyglot repos – Combine stacks in one pass for monorepos.
Related tools
For branch names from ticket titles, use the Git Branch Sanitizer. For environment file layout, see the .env Formatter and Validator.
⭐ Rate this tool
Your feedback helps us improve
🔄 Workflow Suggestion
Try combining multiple tools for a complete workflow. For example: Notepad → Text Encryption → Save to Cloud or Date Calculator → Calendar → Countdown Timer
Related Tools & Recommendations
💡 You might also need
Base64 Encode/Decode
Convert text to Base64 format and decode Base64 strings
JSON Formatter & Validator
Format, validate, and minify JSON data with syntax highlighting and error detection
YAML ⇄ JSON Converter
Convert between YAML and JSON formats with validation and formatting
📁 More Utilities Tools
YAML Formatter and Validator
Format and validate YAML with consistent indentation. No conversion to JSON.
HTTP Request Builder
Build HTTP requests with URL, method, headers, and body. Send or copy as cURL or fetch snippet.
HTTP Headers Parser
Parse raw HTTP response headers into a key-value list. Paste from DevTools, copy single headers or the full block.
Send Feedback
We'd love to hear your thoughts! Your feedback helps us improve our tools and create a better experience for everyone.
Share Your Experience
Tell us what you think about this tool