Screenshots and clips, together
Capture screenshots and record clips from a tab, window, or screen. Draw, blur, or redact screenshots, then arrange up to 20 captures in one shared gallery.
Err + लेख(lekh) = error + written record
Every error, on the record.
Capture the screen, logs, and errors together. Share one link your team can replay and investigate.
Try the buggy demoReview recordings before publishing
demo00:14Shared report
Coupon code fails at checkout
Chrome 129macOS · 1512 × 982
Interactive demo · simulated data00:00 / 00:14
ClickErrorFailed request
- Screen, console, and network
- Redacted before upload
- One replayable link
Why the name
The name explains exactly what the product does.
Err is the problem. लेख (lekh) is the record. Put them together and every bug becomes evidence your team can replay, inspect, and resolve.
Say it: err-lekh
Put a demo error on the recordSelect a part of the name
Together: the written record of an error.
Errlekh turns the screen, console, network activity, environment, and team discussion into one replayable report link.
Product
Capture the moment. Keep the record.
Everything an engineer asks for in the first reply, already written down in the report.
Console + network, attached automatically
Browser, OS, viewport, and URL ship with every report. With Errlekh Capture, every console message, request, error, and click comes too, lined up with the video.
Review web recordings before they upload
In the web recorder the clip stays on your device as a local preview until you choose Publish. In Errlekh Capture, Stop & publish is the publish step; a capture cut short by a closed tab waits in the extension until you publish it.
Comments at the exact second
Teammates reply at a timestamp and the video seeks there. Report access follows your site’s sharing settings.
The next chapter of every error
From “it broke”
to “we checked.”
The recording is the beginning. Errlekh keeps the context connected as you investigate, hand off, and verify the fix.
One continuous recordInteractive example
ERR · EXAMPLE 001Inbox
The moment, with context.
A recording, the browser details, and the technical events. Keep the original evidence within reach.
00:13 · POST /checkout → 500
One replayable report link
Sandbox
Break something. Watch Errlekh write it down.
A simulated page and recorder. Press a trigger and see the entry Errlekh Capture would add to the report, with the time it happened.
Trigger something on this fake page
Each button adds the entry Errlekh Capture would record. The timer starts on your first click.
Errors0Warnings0Clicks00 captured
No console entries yet
Press a trigger to write the first line of the record.
Nothing recorded yet.
Want the real thing? Record the buggy demo checkout with the extension.
How it works
Three steps from bug to report link.
Press Record, pick a tab, window, or screen, and reproduce the issue. With Errlekh Capture the console and network log ride along.
Recording links
Customer context, without the back-and-forth.
Create a recording request, send the link, and get a replayable report instead of a paragraph of guesses.
Nothing to install
Customers record from the link in a current Chrome, Edge, Firefox, or Safari release.
Link expires in 30 days
Every recording link carries a high-entropy token and stops working after 30 days.
The report lands in your workspace
The clip and its context arrive as a report you can review, share, and comment on.
Recording requestDemoExpires in 30 days
Show us the coupon error at checkout
Reproduce the issue on your screen. You will review the clip before anything is sent.
Start recording
Try it: this demo records nothing
Review before sendingNothing to installTab audio optional
Developers
Built for developers and AI agents.
Every report is plain JSON behind a stable URL, and the workspace exposes its actions to browser agents.
terminal
ERRLEKH_URL="https://your-errlekh-host"
# Report: title, environment, Activity timeline, media URL
curl -s "$ERRLEKH_URL/api/reports/5bf72d7647ca4b36"
# Full console + network log from Errlekh Capture (404 when none)
curl -s "$ERRLEKH_URL/api/reports/5bf72d7647ca4b36/logs"Example response (abridged)
{
"report": {
"title": "Coupon code fails at checkout",
"browser": "Chrome 129",
"durationSeconds": 41,
"diagnostics": [{ "at": 3, "kind": "network", "title": "POST … → 500" }],
"mediaUrl": "/api/reports/5bf72d7647ca4b36/media",
"logsUrl": "/api/reports/5bf72d7647ca4b36/logs"
}
}Report JSON API
GET /api/reports/:slug returns the title, environment, the Activity timeline, and URLs for the media and the log.
Console + network log
GET /api/reports/:slug/logs returns every console entry and request Errlekh Capture recorded: levels, stacks, statuses, timings, safe headers. 404 when a report has none.
WebMCP tools
The workspace registers list_issue_reports and prepare_issue_capture, so browser agents can list reports and cue up a capture.
Comments API
GET and POST /api/reports/:slug/comments list and add notes pinned to a second of the recording.
Security
Privacy by design.
Secrets are redacted in the page and again on the server. Type below to run the server’s redaction rules on your own text.
Try a sample
What Errlekh storeslive
POST https://shop.example.com/api/login?token=…&page=… Authorization: Bearer [redacted] password=[redacted] email [email]
2secrets removed1email removed2query values removedRuns the server’s own redaction code, in your browser. Nothing you type is sent.
Never read
Cookies, authorization headers, request bodies, and input values are never read by the extension.
Query values removed
Captured URLs keep their origin and path. Query strings keep parameter names only; values and fragments are dropped.
Bodies only when it matters
Only allowlisted response headers are kept, and response bodies only for failed requests when you turn that on.
Links that can’t be guessed
Share links use long random slugs. Recording links use random tokens and stop working after 30 days.
Nothing uploads until you publish. The web recorder shows a local preview first; Errlekh Capture uploads when you press Stop & publish, and holds a capture that ends any other way until you publish, download, or discard it.
Put every error on the record.
Screen, console, network, and errors in one link your team can replay.
Free to start · Web recordings upload only when you publish