Repository navigation
[Feature Request] Add an option to disable automatic Markdown entries for rich-text clipboard content #336
Description
I'm using PasteBar 0.7.0 on Windows 10.
When I copy formatted text from a WYSIWYG editor, PasteBar creates two separate history entries:
RichText
Markdown
I only need the RichText version. The automatically generated Markdown entry is unnecessary for my workflow and makes the clipboard history more cluttered.
What I have already tried:
In Settings → Clipboard History Settings, I disabled:
- Programming Language Detection
- Special Copy and Paste Operations
I then restarted PasteBar, but the behavior remained unchanged.
I could not find any other setting that controls automatic Markdown generation.
Expected behavior
It would be useful to have an option such as:
Disable automatic Markdown conversion
or:
Do not create Markdown entries from rich-text clipboard content
When disabled, copying formatted content should create only the RichText entry (and the normal clipboard formats), without creating a separate Markdown history item.
Current behavior
Copying formatted WYSIWYG content results in both a RichText and a Markdown entry being added to PasteBar's history.
Environment
PasteBar: 0.7.0
OS: Windows 10
Source: WYSIWYG editor / formatted text (Joplin 3.7.16)
Thank you for considering adding such an option.
Activity
kurdin commentedon Sep 18, 2026
@GagaMaga600
Thank you for the detailed report.
I believe the root of the problem is actually how Joplin handles clipboard operations. It appears that Joplin app is writing to the clipboard twice in rapid succession: first as plain text, and then immediately again as Markdown.
Other clipboard managers like CopyQ likely filter this out by ignoring the first clip because the second one arrives almost instantly. Ultimately, this is a bug on Joplin's end, the app should only write a single, unified copy event to the clipboard rather than triggering two separate ones. I recommend opening an issue on their GitHub repository so they can fix this upstream behavior.
In the meantime, I will add an option to PasteBar to ignore extremely rapid, sequential clipboard copies. Once implemented, this will filter out the double-copy issue and allow PasteBar to handle this scenario similarly to CopyQ.
Thank you again!