transcribe-anything
Multi-backend whisper app. Blazing fast. Mac-arm optimized. Easy install. Input a local file or url and this service will transcribe it using Whisper AI. Completely private and Free 🤯🤯🤯
Runssource: GitHubhomepagePythonMITcommit c4a1808e6acf
Python, MIT licensed. The project labels itself: cli, diarization, python, speech to text, subtitles, transcription and whisper.
transcribe-anything runs. An Argusic agent installed it in 0.2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
transcribe-anything 4.1.2 installs and local CPU whisper transcription works end-to-end on video.mp4, generating correct out.txt/out.srt/out.vtt; the server daemon boots on port 18765 and responds 200 on /healthz and /docs; 262 of 278 tests pass, 13 skip (GPU/MLX backends), 3 fail due to YouTube bot-detection blocking yt-dlp without browser cookies.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 3 tests fail because YouTube blocks yt-dlp --get-title and --download without cookies (bot detection). Tests: test_bad_video_title, test_transcribe_anything::test_fetch_command_installed, test_transcribe_anything_api::test_fetch_command_installed.
- Install time
- under a minute
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- uv run pytest --tb=long -v: 262 passed, 3 failed (YouTube auth), 13 skipped; transcribe_anything tests/localfile/video.mp4 --language en --model tiny produced correct out.txt, out.srt, out.vtt with full transcription text; transcribe-anything-serve returned 200 on /healthz ({"status":"ok"}) and 200 on /docs
- Model tokens used
- 145,885
- Exact commit tested
- c4a1808e6acf
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
FAILED tests/test_transcribe_anything.py::TranscribeAnythingTester::test_fetch_command_installed
FAILED tests/test_transcribe_anything_api.py::TranscribeAnythingApiTester::test_fetch_command_insta…
============ 3 failed, 262 passed, 13 skipped, 4 warnings in 33.47s ============
exit_code=0
All information gathered. Let me compile the final report.
The install succeeded cleanly. The test suite runs at 262 passed, 3 failed, 13 skipped. All 3 failu…
**ARGUSIC_RESULT:**{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.2, "e…
tokens used
145,885
All information gathered. Let me compile the final report.
The install succeeded cleanly. The test suite runs at 262 passed, 3 failed, 13 skipped. All 3 failu…
**ARGUSIC_RESULT:**{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.2, "e…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.2 minutes, faster than the median of the 127 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 128 cli projects Argusic has installed and timed, transcribe-anything was the 6th fastest to reach a running state, and 117 of 128 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
clidiarizationpythonspeech-to-textsubtitlestranscriptionwhisper
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/transcribe-anything)Questions
- Does transcribe-anything run?
- Yes. transcribe-anything runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test transcribe-anything?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c4a1808e6acf. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test transcribe-anything?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does transcribe-anything take to install?
- 0.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does transcribe-anything need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing transcribe-anything?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does transcribe-anything compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, transcribe-anything was the 6th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for transcribe-anything?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.