Guide

THE TOOLBOX / DEVELOPER & DATA

Glob Tester & .gitignore Visualizer —
Debug Wildcards, Negations & File Paths Live.

Test minimatch glob patterns and Git .gitignore rules against real project file trees with instant match, ignore, and un-ignore highlighting—100% locally in your browser.

Preset:
Live Evaluation (5 / 12 Ignored)
src/index.tsTracked
src/components/Button.tsxTracked
src/components/Button.test.tsxTracked
src/styles/globals.cssTracked
public/logo.svgTracked
.env.localIgnored
.env.exampleUn-ignored (!)
dist/bundle.jsIgnored
node_modules/react/index.jsIgnored
docs/README.mdTracked
logs/error.logIgnored
temp/cache.tmpIgnored

GLOB SYNTAX CHEAT SHEET

Common Glob & .gitignore Wildcard Tokens.

TokenMeaningExample
*Any characters except path separator /src/*.ts
**Zero or more nested directories (globstar)src/**/*.tsx
{a,b}Match any listed alternative*.{jpg,png,webp}
!ruleNegate / re-include previously ignored file!.env.example

2. Zero-Upload Privacy

Private repository paths and internal ignore lists never leave your browser tab.

Frequently Asked Questions

What is the difference between * and ** in a glob pattern?

A single asterisk (*) matches any characters within a single directory segment (it stops at /). A double asterisk globstar (**) matches zero or more nested directories recursively, so src/**/*.tsx matches files at any depth under src/.

How does negation (!) work in .gitignore files?

Prefixing a rule with ! re-includes a previously ignored file—for example, .env* followed by !.env.example ignores all environment files except the template. Note that Git cannot re-include a file inside an already-ignored parent directory unless you un-ignore the parent folder first.

Why does my glob pattern skip dotfiles like .env or .github?

By default, POSIX glob libraries hide leading-dot filenames unless dot-matching is explicitly enabled or the pattern itself begins with a literal dot (like .env*). Toggle "Match dotfiles" above to test both behaviors.

What does brace expansion {ts,tsx} do in glob testers?

Brace expansion matches any comma-separated alternative inside curly braces—so **/*.{ts,tsx} matches both TypeScript and TSX files in one compact expression.

Is .gitignore matching identical to minimatch globbing?

No—.gitignore follows Git’s own specification (where a pattern without a slash like *.log matches in every subdirectory, and trailing slashes like dist/ match only directories). Use ".gitignore Mode" for Git rules and "Glob Mode" for Node/Vite/ESLint/CI globs.

Are my repository paths or .gitignore rules sent to a server?

Never. Both minimatch and the Git ignore engine run 100% locally in your browser.