Copy Link Button

approved

by ChekTek

Adds a copy button next to markdown links and bare URLs so you can copy the URL with a single click. - This plugin has not been manually reviewed by Obsidian staff.

↓ 127 downloadsUpdated 1mo agoMIT
Install in ObsidianView on GitHub

Copy Link Button

An Obsidian plugin that adds a small copy button next to links and images, so you can copy their target to your clipboard with a single click — much like the copy button next to code blocks.

Copy button next to a link

Features

  • Adds a copy button next to markdown links ([text](https://…)), bare URLs (https://…), and wikilinks ([[Note|Alias]]).
  • Supports internal embeds (![[image.png]]) and markdown images (![alt](https://…)) with a floating copy button for rendered images.
  • Works in both editing / Live Preview and reading view.
  • Clicking the button copies the URL, wikilink, or image target and briefly shows a checkmark.
  • Buttons are always visible by default, with a setting to only show them while holding Ctrl, Cmd, Alt, or Shift.
  • Styled with Obsidian theme variables, so it matches the external-link icon in light and dark themes.

Installation

From the community plugin store

Once approved: Settings → Community plugins → Browse, search for "Copy Link Button", install, and enable.

Manual

  1. Download main.js, manifest.json, and styles.css from the latest release.
  2. Copy them into your vault at <vault>/.obsidian/plugins/copy-link-button/.
  3. Reload Obsidian and enable the plugin under Settings → Community plugins.

Development

npm install --legacy-peer-deps   # obsidian pins an exact CodeMirror peer dep
npm run dev                       # watch + rebuild main.js

Symlink (or copy) the repo into your vault's plugins folder to test live:

ln -s "$(pwd)" "<vault>/.obsidian/plugins/copy-link-button"

Building

npm run build     # type-check + production build (main.js in repo root)
npm run package   # production build collected into dist/ for distribution

Releasing

Pushing to main runs the release workflow. When the version in manifest.json doesn't yet have a matching git tag, the workflow builds the plugin and publishes a GitHub release (tagged with the bare version, e.g. 1.0.0) with main.js, manifest.json, and styles.css attached.

To cut a release: bump the version in manifest.json (and versions.json / package.json), commit, and push to main.

License

MIT

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.