Craft Link Repair helps you repair supported Craft links in local copies

Name: Craft Link Repair
Author: theluckystrike

Preview Craft link repairs in file copies.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

Three exported pages with proposed local wikilinks and original labels. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 19
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The README reports desktop app tests. Physical phones and tablets were not tested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Craft Link Repair

You want to repair supported Craft links in local copies in your vault.

Put your unpacked Craft export inside the vault and preview its supported page links. Craft Link Repair uses metadata identifiers to find local targets. It writes copies and a report while leaving the source notes in place.

Preview local page and date links, write copies, then open the repair report.

Free features

Preview page links from identifiers

The preview maps metadata identifiers to sibling Markdown pages. Duplicate identifiers and ambiguous siblings remain unresolved rather than producing guessed targets.

Write copies beside source notes

The free pass creates up to 10 new copies with a repaired suffix. A larger pass or a destination conflict stops before writing.

A repaired Atlas note with local page links and its source note preserved. — Open larger

Convert date links

Supported day links become date-note wikilinks with their original labels. Invalid dates remain unresolved, and the converter doesn't create date notes.

The weekly review shows Monday and Friday as date note links. — Open larger

Review unresolved links

The preview reports unresolved supported links and metadata issues. A new report lists written copies, skipped copies and write failures.

The report lists a missing page identifier and a block link for manual repair. — Open larger

The free pass creates up to 10 new Markdown copies.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Saved output paths and date formats Pro

Pro removes the 10-note limit and adds separate output paths and date formats. Simple relative resource paths point back to source assets.

Saved output folder and date format controls enabled with a local sponsor fixture. — Open larger

Repair when new exports arrive Pro

Pro can check for new copies after source Markdown or metadata changes. Automatic repair starts off and doesn't update existing recorded copies.

The automatic pass creates a repaired copy for a new exported page. — Open larger

See how Pro works

Set up Craft Link Repair

needs

Obsidian 1.13.4 or later

steps

Unpack your export inside the vault, keeping Markdown, metadata and assets together.
Run Preview repaired copies from the command palette.
Enter the export folder path and select Preview links.
Review the output paths and select Write copies.
Open the report and follow links in sample repaired notes.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to repair Craft links in Obsidian

Known limits of Craft Link Repair

Reference links, bare URLs, HTML links and separate Craft block targets are outside the supported conversion format.
Missing or duplicate metadata identifiers remain unresolved; labels do not supply page targets.
The free pass stops before writing when it needs more than 10 new copies.
The tool does not import archives, copy attachments or update existing repaired notes.
Separate Pro copies can depend on assets that remain in the source export folder.
Tests use synthetic exports; full customer exports and physical mobile devices were not tested.

Questions about Craft Link Repair

Does this import a Craft archive?

Unpack the export and put its files into the vault first. This tool handles supported local link repair after that step.

Will it find pages from their labels?

Page mapping requires supported metadata identifiers. Missing or duplicate identifiers remain unresolved.

Are attachments copied to my output folder?

The tool leaves attachments in the source export. Simple relative inline resource links are rebased when a Pro copy uses a separate folder.

Can automatic repair update a copy?

Recorded copies are skipped while their destinations exist. Move a copy away before creating another one from a changed source.

Network use

After you select Sign in with GitHub, the plugin sends its client ID, read:user scope and device-flow requests to github.com. Due checks and Refresh send your token to api.github.com to read your sponsorship tier and total payment. No note text, filenames or other vault data goes to either host.

Read the full network disclosure