A meeting cannot be saved as a PDF because it is not a document. What people want is the transcript, the chat, or the attendee list — and each is somewhere different.
Outlook and other mail
| Client | How |
|---|---|
| Outlook desktop | File → Print → Microsoft Print to PDF |
| Outlook web | Three dots → Print → Save as PDF |
| Gmail | Print icon → Destination: Save as PDF |
| Apple Mail | File → Export as PDF |
| Thunderbird | Print → Save as PDF |
Expand the whole thread before printing. Every client collapses quoted history by default, and the printed result contains only what was on screen — a twelve-message exchange saved as two.
What the printed version leaves out
A printed email looks complete and is missing things that matter if the copy is ever needed as evidence.
Attachments are not included — they must be saved separately and, if the record needs to be complete, merged into the same document. The full internet headers are also absent, and those are what carry the routing information, timestamps at each hop and authentication results.
For an ordinary record, printing is fine. For a dispute, a grievance or anything that might be examined, save the original message file as well — a .msg or .eml — because that preserves the headers and the attachments intact. A PDF is a picture of the email; the .eml is the email. Merge PDF combines the message with its attachments when you need one document.
Meetings are not documents
This is why the question has no direct answer. A meeting is an event; a recording is video. Neither converts to a PDF in any meaningful sense.
What people usually want is one of four things, and each lives somewhere different.
- The transcript — what was said. Available if transcription was enabled.
- The chat — messages sent during the meeting.
- The attendee list — who joined and for how long.
- Shared slides — which are a separate file the presenter already has.
Working out which one is wanted takes a moment and saves considerable effort, because three of the four are straightforward and the fourth — a readable record of a video — does not exist as an export.
Google Meet
If transcription was on, the transcript is saved as a Google Doc in the organiser's Drive, in a Meet Recordings folder, and appears attached to the calendar event.
From there it is File → Download → PDF Document. The chat is saved to Drive as well when recording is enabled, and attendance reports are available on certain Workspace editions rather than all of them.
Everything belongs to the organiser's account. If you attended rather than organised, you cannot retrieve any of it yourself and will need to ask — which is worth knowing before the meeting rather than a week after it.
Zoom, and large meetings
Zoom separates the pieces more than Meet does, and for a large session the useful records are in the web portal rather than the app.
Cloud recordings produce an audio transcript as a VTT file, downloadable from the recording page. In-meeting chat saves as a plain text file. Neither is a PDF, and both convert trivially once you have them.
- Transcript: download the VTT, open it in a word processor, tidy the timestamps, export to PDF.
- Chat: the saved .txt, same route.
- Attendees: the web portal's Reports section produces a CSV of participants and join times.
- Registration: also a CSV report, for registered webinars.
- Then merge if the record should be one document.
A VTT is readable but ugly — a timestamp block before every line. Stripping the timestamps takes a find-and-replace and turns it into something a person can actually read, which is usually the point of making a PDF of it at all.
You cannot embed a PDF in an email
Not in the body, and this is worth stating plainly because a great deal of advice implies otherwise.
Email clients render HTML. They do not render PDFs inline, and there is no markup that makes them. A PDF in an email is an attachment, shown as an icon or a preview card depending on the client.
- Attach it. The normal answer, and what recipients expect.
- Convert the first page to an image and inline that, linking the image to the full document. Common in newsletters.
- Rebuild the content as HTML in the email body if it is short.
- Link to it if it is large or will be updated.
The image approach is the closest thing to embedding and has a catch worth knowing: many clients block remote images by default, so the recipient sees an empty box until they choose to load them. Any information that must be read should be in text, with the image as reinforcement rather than the message itself. PDF to JPG renders the page for that use.
Frequently asked questions
How do I save an Outlook email as a PDF?
File → Print, then choose Microsoft Print to PDF as the printer. Expand the whole thread first — clients collapse quoted history by default, and the printed copy contains only what was visible on screen.
Does a printed email include the attachments?
No. Attachments must be saved separately and merged in if the record needs to be complete. The full internet headers are also missing, which matters if the copy might be needed as evidence.
What should I keep if an email might be needed as evidence?
The original message file — a .msg or .eml — alongside any PDF. That preserves the routing headers, timestamps at each hop, authentication results and attachments. A PDF is a picture of the email; the .eml is the email.
How do I save a Google Meet as a PDF?
You cannot save the meeting itself, but if transcription was on the transcript is a Google Doc in the organiser's Drive, under Meet Recordings, and downloads as a PDF from File → Download. Everything belongs to the organiser's account.
How do I get a record of a large Zoom meeting?
The cloud recording produces a VTT transcript, in-meeting chat saves as a text file, and the web portal's Reports section gives a CSV of participants and join times. Convert and merge whichever you need — none is a PDF to start with.
How do I make a VTT transcript readable?
Open it in a word processor and use find-and-replace to strip the timestamp blocks that precede every line. That turns it from a subtitle file into something a person can read, which is usually the reason for exporting it.
Can I embed a PDF inside an email body?
No. Email clients render HTML and cannot display PDFs inline. The nearest approach is converting the first page to an image and linking it to the full document — but many clients block remote images by default, so anything that must be read should be in text.