Inventory slides, embedded media, separate attachments and supporting records before choosing PPT, PDF, original files or a package. Then open the archive offline, check slide and media counts, confirm attachments work, and record the version, permissions and verification result.
A presentation often looks like one file but acts as an index to several materials: slides, notes, images, video, data attachments and external links may all live in different places. Downloading the current deck as a PPT can preserve only part of that package.
Start with the future use. If the final layout only needs to be read, PDF is often more stable. If someone must keep editing, the PPT and its source assets belong together. For project handover, attachments, sources and verification records matter as well.
Five things to inventory
| Item | Where it may live | What to check |
|---|---|---|
| Slides and notes | The presentation itself | Page count, layout, notes and hidden slides |
| Embedded media | Images, audio and video | Whether playback still depends on a remote URL |
| Separate attachments | Document attachments or cloud files | Whether they download independently from the deck |
| External assets | Fonts, templates and source data | Whether another computer can still open them |
| Context | Project notes, reviews and version records | Who approved which version and when |
Not every presentation contains all five. An inventory makes the export route visible before files are scattered across a downloads folder.
What a PPT alone may miss
- Video, audio or fonts may still point to an online environment.
- Attachments linked from the deck may never be downloaded.
- Animation, speaker notes, masters or complex layout may change between formats.
- Without a version and source note, nobody can identify the final copy later.
- The source page may keep changing while the local export has no snapshot date.
The exact result depends on the source file, export format and current Feishu version. Test one real presentation against the inventory before archiving a larger set.
Three practical routes
Save the final presentation only
Download the PPT and keep a PDF beside it. The PDF fixes the layout for reading; the PPT preserves editable content. Give both files the same base name so the pair stays together.
The presentation depends on many attachments
Put images, spreadsheets, video and files in separate folders instead of a temporary downloads directory. Keep original attachments when they can be downloaded. When a visible asset cannot be saved, record its name, source and owner.
For large sets, a package or batch queue is less error-prone than saving items one by one. Test the folder structure on one presentation before processing the project.
Archive the whole project
The deck is only one project artifact. Keep the final approved version, review records, source assets and delivery attachments under one archive root so the next person can reconstruct the context.
Use folders to preserve relationships
2026-10-product-review/
01-presentation/
product-review-final.pptx
product-review-final.pdf
02-media/
images/
videos/
03-attachments/
budget.xlsx
user-research.pdf
04-context/
review-notes.md
approval-record.md
README.mdThe README.md does not need to be long. Record the project name, export date, source version, file purpose, permission boundary and anything that failed to download.
Verify the archive
- Open the PPT and PDF offline.
- Check slide count, hidden slides, notes and important layout.
- Open every media file and attachment, not just the folder.
- Test a few external links to catch temporary URLs.
- Move the whole folder and confirm that paths still work.
If the deck contains pricing, customer material or internal review notes, check who can access the archive. Keep the public presentation separate from internal attachments whenever possible.
A usable presentation archive is not just an openable PPT. Months later, it should still answer which version it is, where the source assets live, whether attachments are complete and who approved it.