Skip to content
Workflows8 min read

Rename Obsidian Attachments: Check Links Before and After

Rename an Obsidian attachment after checking link settings. Distinguish display labels from filenames, then inspect selected notes before a larger cleanup.

·By Taha Baalla

A useful rename keeps two things clear: which file the note opens and what the reader sees. This guide proposes a one-file check before a larger cleanup. It follows current documentation; we have not performed a rename test or verified a particular vault.

Decide whether the filename needs to change

Start with the reason for the cleanup. A file named `scan.pdf` may need a descriptive name because you cannot distinguish it from other scans. But a note that displays a long filename may only need a shorter label in its own sentence.

Those are different changes. The first affects the source's identity in your working file organization. The second changes how one reference reads. Decide which problem you are solving before selecting a file operation.

For a hypothetical research project, imagine two notes that refer to the same PDF: a reading summary and a project checklist. The summary could call it “methods report,” while the checklist calls it “supporting evidence.” Different display wording does not require two copies of the PDF or two competing filenames.

Our research app guide considers broader tool choices. Here the task is maintaining a live relationship between a current note and its current source, not choosing a new app or recovering an older edition.

Understand the target and display text

Obsidian supports Wikilinks and Markdown links. Display text can differ from the destination, non-Markdown targets need their extension, and Markdown destinations require URL encoding, including `%20` for spaces. An exclamation mark before a Wikilink embeds the linked content. Internal-link documentation

The following illustrative values describe the same hypothetical PDF without creating clickable links:

Part of the referenceExample valueWhat it controls
Actual filename`methods report.pdf`Which source file you intend to reference
Markdown destination`methods%20report.pdf`The encoded filename in a Markdown reference
Display labelMethods sourceThe wording visible in the note
PresentationText link or embedWhether the note shows a link or embedded content

Changing the display label does not rename the PDF. Choosing an embed changes presentation; it does not establish that the destination identifies the correct source.

Read the destination when diagnosing a reference. A reassuring label can remain readable even when the target is wrong. Conversely, a link can open the right file while showing wording you would prefer to improve.

Do not copy these examples as a repair without identifying your real filename and location. If your link includes folders, preserve that context when inspecting it; the example intentionally omits folders to keep the distinction visible.

Check one attachment before changing more

Attachments are regular files in a vault, including supported images and PDFs. Obsidian's attachment-location setting controls where newly added attachments are placed. Attachment documentation

Choose a nonessential file for your first check. Open it and identify a recognizable detail, such as the report title or a diagram. Record its current filename and location, your intended new name, and the notes you have selected for inspection.

For the hypothetical project, select both the reading summary and checklist. Inspect their references before renaming so you know whether each already opens the intended PDF. A broken reference found at this stage is an existing problem, not evidence that the planned rename caused it.

Use precise observations:

  • “Summary opens the methods report; displayed label is too long.”
  • “Checklist opens a different report with a similar name.”
  • “PDF opens directly, but the summary's link is unresolved.”

These are example observations to guide your own check, not results from a tested vault. Establish the baseline before attempting to improve it.

Inspect the setting, then rename inside Obsidian

Under Settings → Files and links, inspect Automatically update internal links. Obsidian says enabling it updates internal links when a file is renamed; disabling it makes Obsidian prompt about updating links. Files and links settings

On desktop, for the documented File explorer operation, right-click the file, choose Rename, enter the new name and press Enter. File explorer instructions

Keep the file extension appropriate to the original format. For example, choose a descriptive PDF name that still ends in `.pdf`; changing a suffix is not a document conversion. For this initial check, avoid combining a rename with a folder move or unrelated edits. One deliberate change makes an unexpected result easier to interpret.

Inspect any prompt before accepting it. The objective is not to click through a cleanup quickly, but to understand which source you are renaming and whether the references you care about remain useful.

This procedure stays within the documented in-app rename workflow. It does not establish equivalent behavior for renames made by another application or while Obsidian is closed.

Check every note you selected for the pilot

Return to the reading summary and project checklist. In each, inspect the reference destination, open the attachment and confirm the recognizable detail you checked earlier. If one reference is an embed, inspect that presentation as well as the file itself.

Check the prose around the link too. An updated destination does not necessarily make a vague sentence understandable. If the summary now reads naturally but the checklist still says “this document,” improve that local wording without making another unnecessary source rename.

Record the scope of your result: “Both selected notes open the intended report after this rename.” That statement describes the inspection you performed. It does not certify every link across a large vault, external exports, other applications or devices you did not inspect.

If cross-device reading is part of the task, verify the intended device separately before expanding the cleanup. Our iPhone and Mac sync guide addresses that wider workflow; a successful local rename alone does not demonstrate delivery elsewhere.

Treat already-broken links as an identity problem

Do not assume switching on an update setting can determine what an old unresolved reference was meant to open. First identify the real source. Compare its content with the surrounding note, the original filename you recorded and any available project context.

If two PDFs could plausibly match, leave the ambiguity explicit. A link that opens the wrong source can be more misleading than a visibly unresolved one. Once you have established the correct file, repair that individual reference and reopen it to check your choice.

Avoid a vault-wide text replacement based solely on a common filename fragment. The same words may appear in descriptions, unrelated destinations or notes about different documents. An individual repair with an understood target is a better starting point for deciding whether a repeated pattern actually exists.

Changing the default folder for new attachments also does not, by itself, demonstrate that existing files moved or earlier links were repaired. Keep naming, location and reference repair as separate decisions until you understand their effects.

Stop the cleanup when the reference is clear

A useful naming convention should help you recognize a source without repeatedly reorganizing it. Prefer enough information to distinguish similar files, and use local display wording for the context of a particular note.

For ongoing reading, our iPhone research workflow connects capture with review. Add this one-file link check when improving filenames, then expand only after understanding the observed result.

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 do not establish Obsidian integration, link repair or vault import. Keep maintenance decisions grounded in the actual notes and attachments you inspect.

FAQ

Can I change the displayed link name without renaming the PDF?

Yes. Use display text for wording that belongs to one note's context. Check the destination separately so your clearer label still refers to the intended source. A cosmetic improvement should not conceal uncertainty about the actual file.

Does enabling automatic updates repair all my old broken links?

Do not assume it does. The documented behavior concerns renaming a file; already-unresolved references still need their intended targets identified. Inspect and repair a known example before considering a wider change.

Can I rename attachments outside Obsidian and expect the same result?

This guide does not establish that guarantee. Use the documented in-app operation for the proposed check, then inspect your selected references. Treat external or closed-app changes as a separate case rather than extending the result of an in-app rename.

Sources

Last reviewed: 2026-11-14. Documentation-backed guidance with hypothetical examples and proposed reader checks; no performed rename test.

TB
·Founder, Nemos

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
Free on iPhone and iPad

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

More from the blog

Add Nemos as a preferred source on Google