Regex Debugger — Test & Debug Patterns
Test regular expressions against sample text and see all matches, groups, and indices in real time.
How it works
- 1Paste or type your text in the input field
- 2Click "Debug Regex" — processing happens in your browser
- 3Copy the result or download as a text file
What to do next
About Regex Debugger
Regex Debugger is built for developer utility jobs that fit cleanly into a browser tab. Test regular expressions against sample text and see all matches, groups, and indices in real time. The processing runs in the page itself, which is why the controls update instantly when you change settings and why a freshly loaded page is ready to do real work the moment it becomes interactive.
Regex Debugger is implemented on top of standard browser APIs. Inputs are read from the file picker or drop zone, decoded in the browser, processed, and re-encoded into the output format. Files up to 0 MB are well within the comfort zone of any modern browser.
Regex Debugger runs the entire transformation inside your browser. The file is read by JavaScript running in the page, processed in-memory by standard browser APIs, and written back as a download. The browser is the runtime; the page is the interface. You can confirm what the tool does by opening the developer-tools Network tab during a run — the only requests are for the page's own static assets.
Anyone who works with developer utility on a casual basis — data analysts wrangling JSON, QA engineers writing repro cases, site reliability engineers triaging logs — finds Regex Debugger a quick way to get the result. The page loads in under a second, the controls are visible from a single screen, and the result downloads or copies in one click.
Regex Debugger works well as a bookmarked utility you reach for when you need it. The first visit shows you what the tool does; the second is when you realise it is a low-friction option for the task and worth keeping in your tab list.
The architecture imposes only the limits the browser itself imposes. The published 0 MB ceiling is conservative; most modern devices comfortably handle inputs up to that size, and the cap exists so the tool degrades gracefully on phones and budget laptops rather than running out of memory.
Even on its own, Regex Debugger composes well with the rest of your toolkit. The output is a standard developer file that opens in any program that handles the format, so the result of one run can become the input to whatever step you use next.
Some notes on the design of Regex Debugger. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
The output handed back by Regex Debugger is the output file. If you would prefer to keep the result in the browser instead of downloading it, you can copy it from the result panel and paste it directly into another tab — useful when the next tool in your workflow expects pasted text rather than a file.
A short note on how Regex Debugger came to look the way it does: every iteration started by watching how someone unfamiliar with the tool actually used it, then removing whatever got in their way. That is why the upload area dominates the screen, the run button is bigger than the secondary controls, and the result panel is unmissable when the job finishes.
As a single-page tool, Regex Debugger stays focused on one developer utility step. Multi-step workflows are composed by chaining adjacent tools — each tool produces a standard file the next one can read directly, so a longer pipeline is just a sequence of short tab-and-tab visits.
Pro tip: Regex Debugger works just as well in a private/incognito window as in a normal one, which is occasionally useful when you want zero browser-history footprint of the job. Another tip: if the tool ever feels slow, it is almost always because the browser tab is competing for CPU with another tab — pausing or closing the heavy ones gives the engine room to work.
If Regex Debugger appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 0 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
Open the workspace above to start using Regex Debugger. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
How it works
- 1Open the Regex Debugger workspace above. The interface is a single page, so there is nothing to navigate.
- 2Select the developer file you want to process — drag-and-drop and the file picker both work.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Hit the run button. standard browser APIs does the work in your browser tab.
- 5Download the result. The file is generated in your browser and saved through your normal download flow.
- 6Repeat the process for additional inputs whenever you need to. The page stays loaded, so subsequent runs are quick.
Common use cases
- Encode binary content for transport in a JSON body using Regex Debugger.
- Hash a string for a quick reproducibility check.
- Convert between data formats while wiring up an integration.
- Decode a token to confirm its claims during a debugging session.
- Inspect a payload during local development without writing a script.
- Generate a quick fixture without leaving the browser.
- Inspect a regex against a test string before committing it.
- Validate a config blob before pushing to staging.
- Compare two API responses to spot a regression.
- Generate boilerplate from a single specification line.
FAQ
How do I enter the regex?
Enter it as /pattern/flags (e.g. /\d+/g) or just the pattern with flags separated by a space.
How do I provide a test string?
You can select a sample from the dropdown or enter your regex on line 1 and your test string on line 2+ of the input.
What are capture groups?
Parentheses in regex create capture groups. Each match shows its full match plus any captured sub-expressions.
Does it show match indices?
Yes — each match shows its starting index within the test string.
Is my data private?
Yes — all matching runs in your browser with no server communication.
What regex flavor is used?
JavaScript's built-in RegExp engine, which supports most common regex features including lookahead and lookbehind.
How long does Regex Debugger take to process a file?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 0 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
Are there any usage limits on Regex Debugger?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Regex Debugger as often as you need; every run produces a full-quality result.
How long does Favtoo retain my data after using Regex Debugger?
Favtoo keeps no copy of your file because Favtoo never receives your file. Regex Debugger runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
Does Regex Debugger require a browser extension or plug-in?
No installation is needed. Regex Debugger runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Regex Debugger on any computer you have temporary access to without leaving anything installed on it.
Does Regex Debugger need an internet connection to run?
Once the page is loaded, Regex Debugger can complete jobs without an active internet connection — the engine is bundled with the page, so there is no per-job network call. The initial page load does require a connection (to fetch the static assets), but after that you can disconnect entirely and the tool will still work. This is a side-effect of the local-first architecture, not a deliberate "offline mode" feature.
How do I run Regex Debugger over a folder of files?
Regex Debugger processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Is Regex Debugger licensed for business use?
Regex Debugger can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Why use Regex Debugger instead of a paid online tool?
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. Regex Debugger sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common developer utility operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.