No Paste

approved

by 观自

Blocks paste actions in Markdown editors while the plugin is enabled. - This plugin has not been manually reviewed by Obsidian staff.

↓ 66 downloadsUpdated 2mo agoMIT
Install in ObsidianView on GitHub

No Paste

No Paste is a minimal Obsidian plugin that blocks paste actions in Markdown editors while the plugin is enabled.

What it does

  • Blocks paste events in Obsidian Markdown editing surfaces.
  • Shows a short notice when pasted text is rejected.
  • Works automatically after the plugin is enabled.
  • Does not add commands, ribbon buttons, context-menu items, or settings.

What it does not do

No Paste is not an originality detector, AI detector, or anti-cheat system. It only prevents normal paste actions inside the Markdown editor. It does not claim to block every possible way to insert text, such as file imports, sync, drag-and-drop, external automation, plugin APIs, or direct file edits outside Obsidian.

Use case

Use this plugin when you want a writing space that encourages manual typing and rewriting instead of copying text into the editor.

Installation

From Obsidian Community Plugins

After the plugin is accepted into the Obsidian community plugin directory:

  1. Open Settings → Community plugins.
  2. Search for No Paste.
  3. Install and enable the plugin.

Manual installation

  1. Download main.js, manifest.json, and styles.css from the latest GitHub release.
  2. Create this folder in your vault: .obsidian/plugins/no-paste/.
  3. Put the downloaded files in that folder.
  4. Reload Obsidian and enable No Paste in Settings → Community plugins.

Privacy

No Paste does not send network requests, upload note content, store note content, or save plugin settings.

Development

npm install
npm run dev

Build a release bundle:

npm run build

The release assets are:

  • main.js
  • manifest.json
  • styles.css

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.