Test a flow
Start testing → inspect requests, flag useful evidence, and save screenshots → Finish.
Results open here · detailed report optionalDesktop Chrome · ZIP download · Install with Load unpacked
Unzip the download, then open chrome://extensions in Chrome. Turn on Developer mode, choose Load unpacked, and select the unzipped folder.
Open the app you want to test. Click the extension icon and choose Start testing before reproducing the issue. Use the floating controls to inspect Network, flag relevant requests, pause/resume, or save an annotated screenshot. Drag the control card to move it.
Click Finish to stop recording and open your evidence in Ramupod. Review requests and screenshots before sharing. Add a detailed report if needed, or download the capture for later.
Keep DevTools closed while testing. Chrome displays a debugging notice during capture. Only requests made after Start testing are recorded; requests made while paused are skipped.
Just need an image? Choose Capture screenshot from the extension to select an area, annotate, and download a PNG without starting network capture.
Up to 250 requests, 15 minutes, 64 KiB per text body, and 4 MiB of session evidence. Save up to 2 screenshots per session. WebSocket frames, full streams, service-worker detail, and console logs are not supported.
This is an unpacked extension, not a Chrome Web Store install. Testing uses Chrome debugging permission; controls and screenshots use temporary access to the active tab. Review redacted text and screenshots before exporting.
In the extension, open Settings & saved capture and set Open testing results in to dotools.com or localhost:3000. These are the two supported viewer origins.
Choose Download saved capture in the extension settings, then use Import capture / HAR on this page. The alternative DevTools panel is also available; that capture mode requires DevTools open.
Finish a test in the extension to open its results here automatically, or import a capture to review.
Start testing → inspect requests, flag useful evidence, and save screenshots → Finish.
Results open here · detailed report optionalClick or drag an area, annotate the screenshot, then download the PNG.
Standalone screenshots save directly to your deviceLocal processing · No upload or automatic replay · Only requests recorded during testing are available
Quick capture uses the desktop Chrome extension toolbar and Chrome debugging permission. Keep DevTools closed in quick mode; the alternative DevTools panel requires DevTools open. Start recording before reproducing the bug; prior requests are not recovered. Import the local capture JSON or HAR into this viewer. Missing, oversized, binary, and streaming bodies are explicitly marked. The web viewer does not access other tabs, fetch imported URLs, replay requests, upload evidence, or infer root cause. Review automatic redaction and screenshots before exporting; it is not a guarantee that all sensitive data is removed. Environment and build version are manual inputs. Reports may require fresh credentials and matching application state to reproduce.