Obsidian Attachment Version History: Keep the Source Behind an Older Note
An older Obsidian note may outlast the PDF revision it cites. Distinguish attachment history, snapshots and missing device copies before relying on recovery.
The practical question is not just whether you can recover a note. It is whether you can still examine the source that supported the note at the time you wrote it. This guide proposes a way to keep that relationship clear, using a hypothetical example rather than a performed recovery test.
Give a research note two dates
A note's editing date and its source's version date answer different questions. The first tells you when your interpretation changed. The second identifies the material you interpreted.
For example, a note might summarize a PDF report downloaded before its publisher corrected a table. Later, the same attachment filename might contain the revised report. The link still points somewhere useful, but it no longer proves which table you originally read.
Write down both dates when the distinction matters. Include the source title, its published version or revision label if available, the original URL and the specific page or figure used. These are proposed reference details, not fields Obsidian automatically verifies for you.
Our research app guide covers choosing tools for research. This workflow concerns a smaller responsibility that remains yours across tools: keeping an interpretation connected to the evidence behind it.
Understand which history you are looking at
Current Obsidian documentation lists note-version retention as one month on Sync Standard and twelve months on Sync Plus. Attachment revisions have the shorter window described above. Version history lets you inspect available versions; restoring one replaces the file's contents. Sync version history
File recovery is a separate local mechanism. Its snapshots remain on the device that created them and do not sync between devices. It supports `.md` and `.canvas`, not PDF or image restoration, and is not a complete backup. File recovery documentation
Use those distinctions to name what you have actually found:
| What you found | What it helps establish | What remains unverified |
|---|---|---|
| A past note version | Your earlier wording | The matching source file's bytes |
| A past attachment version | An available earlier source | Whether it is the version your note used |
| A local note snapshot | Text captured on that device | A corresponding PDF or image revision |
The table is a decision aid, not a promise that a particular version exists. Availability must be inspected for the actual file.
Work through a hypothetical day-21 question
Imagine this sequence for a project:
- On day 0, you save a report as `source.pdf` and write a note about a number on page 8.
- On day 3, you replace that attachment with a corrected report while keeping the same filename.
- On day 21, a colleague asks which report supported your original number.
Even if the earlier note is available, that does not establish that the superseded source can still be retrieved through attachment history. The example deliberately puts discovery well after the replacement. It illustrates a planning problem, not a measured test of a vault or a prediction of exactly when an individual version disappears.
The current PDF could be perfectly readable throughout. The missing evidence would be the earlier edition, not necessarily a missing current attachment. That is why a successful link or a readable current file does not answer the colleague's historical question.
A stronger reference would identify the original report's revision and retain an independently preserved copy. You could then compare the page cited in the note against the correct edition rather than trying to infer it from your summary.
Preserve the note and source as a meaningful pair
When a source's wording or figures are important enough to cite, record the association while you can still inspect it. A compact reference note might contain:
- Interpretation: your own conclusion, clearly labeled as yours.
- Source identity: title, author or organization, URL and available revision label.
- Evidence location: page, section, figure or quoted passage.
- Source copy: the actual retained file's location, not merely a live URL.
- Verification date: when you opened that copy and checked the relevant evidence.
Keep an earlier source distinct from a newer edition instead of silently replacing it in a preservation set. Use descriptive names and a short explanation of why both editions matter. A date in a filename is useful for navigation, but it is not proof that the file contains the edition claimed; open it and inspect the identifying details.
Retain the pair independently of changes propagating through the active working vault. Choose a backup or preservation arrangement whose actual version scope and retention match how long you might need to defend the reference. This is a selection criterion, not an endorsement of a provider or a claim that a particular copy is already safe.
For the hypothetical report, the useful inspection is narrow: does the retained original contain the number on page 8, and does the accompanying note identify that edition? You do not need to restore a whole vault to ask that question.
If the attachment is missing on another device, check a different branch
An absent device copy is not automatically an expired revision. Obsidian Sync offers selective file-type and folder settings, configured per device. Inspect the relevant PDF or image selection and exclusions on each device before drawing a conclusion about loss. Selective syncing
Also distinguish files that never arrived from files whose contents changed. For the first problem, identify a device where the expected file still opens and record the sync state and any errors. For the second, identify the desired edition and inspect available history or an independent retained copy.
Do not use an older incident report as proof of a current Sync defect. A symptom such as “PDF missing on the phone” does not identify its cause. Keep the observed symptom, configuration and desired outcome separate in your troubleshooting notes.
Our iPhone and Mac sync guide addresses the wider cross-device workflow. The historical-reference question here remains separate: which source edition do you need, and where can you still inspect it?
Choose retention for when you will notice a problem
Consider the interval between using a source and checking it again. Weekly reading notes and a report reviewed each quarter create different discovery delays. A preservation arrangement should reflect that delay rather than the frequency with which you edit the note.
Before relying on a copy, open the relevant note and source together and check the evidence location. Record what remains unknown. “Earlier note found; original report edition not verified” is a useful result because it prevents an incomplete recovery from becoming an unsupported claim.
If you inspect available history, preserve your current work before deciding to replace anything. Do not restore merely to see what happens, bulk-revert unrelated files or delete the current edition to force a recovery attempt. Follow the current official instructions for the specific operation you choose.
For ongoing reading, our iPhone research workflow helps connect capture with review. Add source-edition checks where the original evidence will matter beyond the next reading session.
Nemos is our own app, so weigh what we say about it with that in mind. Nemos keeps links, notes, screenshots and files in one library. Nemos lets you search saved links, notes and text in screenshots.
Those capabilities can support a separate working-reference collection. They do not establish Obsidian integration, vault import, synchronized revision retention or restoration. Preserve the source pair through a method you have actually checked.
FAQ
Will my current PDF disappear after two weeks?
The documented window concerns older attachment versions. Do not interpret it as a scheduled deletion of the current PDF. If a current file is absent, investigate its location and delivery separately from the question of which past editions remain available.
Can File recovery retrieve my older PDF or image?
No. File recovery supports .md and .canvas files, not PDFs or images. Inspect the mechanisms that cover your source file and any independently retained copy. Recovering your wording and recovering its original evidence are different tasks.
Is a longer note-history plan enough for long-term references?
Evaluate the source file as well as the note. Define how long you might need an earlier edition, then check whether your preservation method covers both parts for that interval. A plan's note-history headline alone cannot verify the specific source you need.
Sources
Last reviewed: 2026-11-13. Documentation-backed guidance with a hypothetical timeline and proposed checks; no performed restoration or recovery test.
Taha built Nemos after years of losing screenshots and voice memos across a dozen apps. He writes about on-device AI, personal knowledge management, and building privacy-first tools for iPhone.
@nemosapp
Stop losing things you save.
Nemos remembers every screenshot, voice memo, link, and note — and surfaces them when you need them. Free, private, on-device AI.
Free to download · No credit card · Sign in with Apple