Five practical tools to try locally
A small first test can tell you more than a star count. This edition focuses on local workflows, with a specific task and a catch to check for each. These picks are documentation research, not hands-on test results.
microsoft/playwright
Test a repeatable browser journey with an explicit assertion.
First trial: Use a page you control and check that an expected heading appears.
Check first: Browser binaries and selectors need maintenance.
Original documentationggml-org/whisper.cpp
Explore local transcription with a documented CPU-only path.
First trial: Transcribe a short recording you own and compare proper names against the audio.
Check first: Model size and backend selection change memory needs and speed.
Original documentationdocling-project/docling
Convert documents into structured output for a downstream workflow.
First trial: Inspect one difficult table and reading order in a representative document.
Check first: A successful conversion is not proof that its structure is correct.
Original documentationmifi/lossless-cut
Trim existing footage without building a full editing pipeline.
First trial: Cut a copy of a clip, then inspect its start and end in a player.
Check first: Lossless trimming is not automatic highlight selection or captioning.
Original documentationffmpegwasm/ffmpeg.wasm
Explore media conversion inside a browser application.
First trial: Convert a short sample you own and inspect the output and browser memory use.
Check first: Browser memory and speed differ from native FFmpeg; check the core and wrapper license scopes.
Original documentation