Skip to content
MinuteHaul

How to back up your tl;dv meetings

Context: tl;dv's help center says "Right now, we don't support bulk transcript downloads or exports", and the "Allow downloading meetings in bulk" request on its public feature board is marked "in progress" (checked Oct 2026).

Why keep your own backup

Your transcripts are useful records: customer commitments, interview notes, decisions. A local or cloud-drive copy protects you against plan changes, account issues, or switching tools.

A simple backup routine

  1. First run: export your full history (transcripts plus an index CSV).
  2. Then monthly: export only the last month. The tl;dv API's meeting list accepts from and to dates, and MinuteHaul exposes them as a date range.
  3. Store it in a dated folder, e.g. tldv-backup/2026-10/, in Google Drive, Dropbox or OneDrive.
  4. Before any plan change, run a final export (why).

What gets backed up

Each Markdown file can also include tl;dv's AI notes for that meeting when the API returns them.

Video recordings are not included in the first version.

Pre-order MinuteHaul: $29 one-time or try it free on your 10 most recent meetings

Pre-order: the exporter ships within 7 days of your purchase. If it is not delivered to you in that time, you get an automatic full refund. Requires a paid tl;dv plan with API access: per tl;dv's API docs, the meeting organizer must be on Pro, Business or Enterprise.

FAQ

How often should I back up tl;dv transcripts? A full export once, then a monthly export of the latest meetings, plus a final export before any plan change, is a simple routine.

Can I back up only a date range? Yes. The tl;dv API's meeting list accepts from and to dates, and MinuteHaul lets you set them.

Where should I store the backup? Anywhere you control, such as Google Drive, Dropbox, OneDrive or a local disk.

Are recordings included? No. MinuteHaul's first version backs up transcripts and meeting metadata only.

Related guides

Last checked: Oct 17, 2026. tl;dv features and plans change; verify against tl;dv's own help center before relying on details here.