Every meeting in talat can be exported as a Markdown file, a PDF, or copied straight to the clipboard. You can do it per-meeting on demand, or configure talat to write every finished meeting to a folder automatically.

## Manual export

Click the download button on any meeting to open the export menu. Pick which sections to include (**Notes**, **Summary**, **Transcript**, and **Timestamps**), then choose one of three destinations:

- **Copy.** Puts the formatted Markdown on your clipboard.
- **Save as Markdown.** Writes a .md file to a location you pick.
- **Save as PDF.** Renders the same content to PDF.

Timestamps are only available when Transcript is ticked. The Summary option is disabled if the meeting has no summary yet.

## Auto-export

Auto-export writes every finished meeting to a folder of your choice as a Markdown file, without you having to open each meeting. It fires once post-processing is complete, so the exported file always contains the final summary and title.

To turn it on, open _Settings → Exports_:

1. Tick **Auto-export**.
2. Choose the destination folder. This can be any folder on your machine, including a subfolder of your Obsidian vault. See [Obsidian](/content/docs/integrations/obsidian/index.html) for that setup.
3. Pick which sections to include. The options match manual export: Notes, Summary, Transcript, Timestamps.
4. Optionally tick **Audio recording** to copy the original audio file to the export folder next to each Markdown file. This requires audio recording to be enabled under [Settings → Audio](/content/docs/settings/audio-recordings/index.html).

Filenames are `YYYY-MM-DD-HH-MM-<slug>.md`, based on the meeting’s start time and title. If audio is copied too, it gets the same base filename with the matching audio extension.

## Pushing to an HTTP endpoint instead

If you want finished meetings delivered to a web service rather than a folder, use the [webhook integration](/content/docs/integrations/webhook/index.html) instead. It fires on the same event as auto-export and supports either Markdown or a structured JSON payload.