Built for your work
Is Autorec the right recorder for UX research?
This is a short product-fit page, not a methods guide. If you run remote user interviews and you are weighing recording tools, here is the honest read on where Autorec helps and where it doesn't. For the full interview workflow, the blog post linked below goes deep.
What makes interview recording different
A research interview only works if the participant talks freely, and a recording assistant sitting in the attendee list is a small but real reminder that they are being observed. It can make people more careful and less candid right when you want the opposite. The other half of the job is afterwards: an interview you can't search is an interview you can't really use. The value is in finding the moment a participant said the thing, pulling the exact quote, and tracing a theme across six sessions. That needs a transcript, not just an audio file.
Candor during, quotes afterwards
Autorec records the call window from your desktop and does not join as a participant, so there is no notetaker bot for your interviewee to react to. The session feels like a normal conversation. Afterwards it transcribes locally and writes a .txt transcript plus a timestamped .srt file, which gives you something searchable: you can scan for a phrase, jump to the timestamp in the recording, and lift a verbatim quote for your report. Across a study, that turns a pile of recordings into an archive you can actually mine for patterns.
Plainly: Autorec is a recorder and a transcriber, not a research repository. It does not tag, code, or theme your transcripts, and it has no analysis or affinity-mapping features. It produces clean source material. The analysis happens in your own tools.
The parts that matter for interviews
No bot joins the call
Autorec captures the meeting window from your desktop. No extra participant appears in the attendee list, so nobody on the call sees a recording assistant.
Transcribes on-device
After a call, Autorec runs whisper.cpp locally to produce a text transcript. The audio is never sent anywhere to be transcribed.
Plain .txt and .srt output
Transcripts are written as a .txt file and a timestamped .srt file. Both are standard formats you can open, search, and cite without proprietary software.
Nothing leaves your machine
Recording, transcript, and summary are written to your local disk. No upload step, no vendor copy, no telemetry phoning home.
Where Autorec will not fit a research team
Autorec is single-user. There is no shared team library, so a research team that wants everyone working from one interview archive will find it a poor fit, and a dedicated research repository is the better tool there. It does not do speaker diarization, tagging, or analysis; the transcript is raw text. There is no mobile app, and macOS is still in development. It runs on Linux and Windows.
The full interview workflow
This page is just the product-fit summary. The blog post walks through the whole thing end to end: consent, running the session, getting from a recording to coded findings, and pulling quotes for a report.
Read the full UX research interview workflowQuestions UX researchers ask
Will a recording bot show up in my interview?
No. Autorec captures the meeting window from your desktop and does not join the call as a participant. Your interviewee sees a normal session, which keeps things more relaxed and more candid.
Does Autorec do diarization or tag who said what?
No. The transcript is plain text without speaker labels, and Autorec does not tag or code anything. It gives you a clean, searchable source transcript; coding and analysis happen in your own research tools.
Should I read this page or the blog post?
Read this page to decide whether Autorec fits your tooling. Read the blog post for the actual interview workflow: consent, running sessions, and getting from recordings to findings. The two are meant to be used together.
Try it on your next interview
Free for three recordings a day, up to 40 minutes each. No account, nothing uploaded.
Download Autorec free