← HomeBlog

Changelog

What we've shipped, newest first.

27 July 2026

  • Custom summary instructions, like asking for emojis or a different tone, are now followed instead of sometimes being ignored.
  • You can now see the full history of a transcript's summary versions, in order, on both the web app and Android.

13 July 2026

  • Chat with your transcript: ask a question about a completed job and get an answer grounded in the recording, billed per answer.
  • Assistant replies in chat now render bold, italic, and code properly instead of showing raw asterisks.
  • Re-summarize a transcript with a different style or your own custom prompt, and page back through earlier summary versions.
  • Re-transcribe a job if something got missed or mistranscribed, with a reason attached.
  • Download a transcript and summary as a Markdown or Word file.
  • Save transcripts and summaries straight to Google Drive as a Google Doc, Word file, or Markdown file.
  • Pick which Google Drive folder your exports save into, using Google's own folder picker.
  • Your screen now stays awake while recording, and recording pauses instead of capturing dead air if you switch away.
  • A dismissible tip suggests your phone's voice memo app for long recordings.
  • The job page has a cleaner layout with separated sections, especially on mobile.
  • If a summary fails to generate, you now see a clear message instead of a blank summary.
  • The job page shows when a recording was made.

20 June 2026

  • Added Sign in with Google as an alternative to magic-link.
  • Magic-link emails now survive email-security scanners that previously consumed the link before you could tap it.
  • Redirected www.transcribe-it.co.za to the apex domain so session cookies always land in the right place.
  • Added a help page at /how-to-record covering iPhone, Android, and desktop.
  • Disabled the in-browser recorder on production while we improve its reliability when phones sleep — share from your phone's voice memo app instead.

Looking for the longer version? The blog has the why behind each change.