Private browser tools · browser-local

Aftermath Labs: interactive browser tools that stay local

Choose a private browser utility, local media-capture workflow, input test, or device diagnostic without creating an account.

Work happens in the current browser. The route does not require an account or a server-side processing job.

Browse all Labs →Back to Labs

Task-first navigation

Find the right browser tool without a crowded toolbar.

Use the direct routes below for a focused workspace. Each route exposes its own browser compatibility, permission, and local-data boundary before a device or media action begins.

What it does

Useful, focused capabilities

Fifteen interactive browser tools grouped into two focused collections
Text, developer, timer, QR, and decision utilities
Screen capture, device checks, and live input tests
No account required for the supplied tool workflows

Browser compatibility

Requirements and honest fallbacks

A modern JavaScript-enabled browser; individual tools disclose any hardware, permission, or secure-context requirement before use.

JavaScript-enabled modern browser
Camera
microphone
screen sharing
local storage
download support

Questions people ask

Clear answers and limits

Do Labs tools send my work to a server?

The supplied implementations process their tool inputs in the current browser and contain no tool-content upload endpoint. Production shell changes still need their own network and privacy audit.

Which Labs tools can ask for device permission?

Voice Recorder can request microphone access; Camera & Microphone Test can request camera and microphone access; Screen Recorder can request a display source and optional microphone or camera access.

Do I need an account to use a Lab?

No. The supplied Lab workflows are designed to run without an account. Some tools can optionally keep local history in the browser when storage is available.

How it works · Privacy · Terms of use · Contact