I appreciate the polish for non-technical folks, but "clipboard formatter" feels like a feature, not a product. All of this can be done with AutoHotKey script for Windows and similar open-source tools for the other OS. And given how sensitive is clipboard data (passwords, keys, etc.) using a third-party app feels a bit uncomfortable.
You're absolutely right that you can script this if you have the know-how. I used AHK for years before building this.
But the main goal here is to offer that power to people who don't have the time or desire to learn scripting syntax, set up environments or debug code. They just want a tool that works out of the box. And even for technical folks, maintaining a script that parses complex HTML/RTF without breaking on nested tags (which often happens with Regex) is a headache I wanted to solve permanently.
Regarding privacy, that was actually my top priority when designing the architecture. I'm fully aware of how sensitive clipboard data is, which is why I built it to run 100% locally. You can literally block the app in your firewall or physically disconnect your internet and it works perfectly, I even built an offline license activation method specifically for high-security environments.
As a point of validation, I would use this even though I have know about AHK for years. I don’t have any interest in developing an AHK hobby and I value the specific single feature “strip non-bold/italic/underline/hyperlink formatting”. Thanks for making it :)
That exact feature, keeping the structure (bold/italic...) but stripping the junk was actually the hardest part to build. It requires parsing the full object tree recursively to make it compatible with any app, instead of just doing simple text replacements.
I saw so many people looking for that "middle ground" that I basically built the whole app around it. Glad it resonates!
You'll do better showing this to the people who would be your users. Looks like a solid idea to make some money on the side solving a problem you actually have.
A lot of people on HN wouldn't be your users. That's fine. Find them and post this there.
Thanks! Right now it's Windows only because it hooks deep into the system to handle the formatting and transformation properly, which is totally different on Mac.
However, a macOS version is the #1 request I get. It is definitely on the roadmap! If you want, you can drop your email in the form at the very bottom of the site (under "Don't Miss What's Next") and I'll notify you specifically when the MacOS version is ready.
There's now a CLI that'll read and update your (Mac) clipboard with the result. For this italic use case you'll have to edit the source but it won't be that bad.
I appreciate the polish for non-technical folks, but "clipboard formatter" feels like a feature, not a product. All of this can be done with AutoHotKey script for Windows and similar open-source tools for the other OS. And given how sensitive is clipboard data (passwords, keys, etc.) using a third-party app feels a bit uncomfortable.
You're absolutely right that you can script this if you have the know-how. I used AHK for years before building this.
But the main goal here is to offer that power to people who don't have the time or desire to learn scripting syntax, set up environments or debug code. They just want a tool that works out of the box. And even for technical folks, maintaining a script that parses complex HTML/RTF without breaking on nested tags (which often happens with Regex) is a headache I wanted to solve permanently.
Regarding privacy, that was actually my top priority when designing the architecture. I'm fully aware of how sensitive clipboard data is, which is why I built it to run 100% locally. You can literally block the app in your firewall or physically disconnect your internet and it works perfectly, I even built an offline license activation method specifically for high-security environments.
As a point of validation, I would use this even though I have know about AHK for years. I don’t have any interest in developing an AHK hobby and I value the specific single feature “strip non-bold/italic/underline/hyperlink formatting”. Thanks for making it :)
Thanks!
That exact feature, keeping the structure (bold/italic...) but stripping the junk was actually the hardest part to build. It requires parsing the full object tree recursively to make it compatible with any app, instead of just doing simple text replacements.
I saw so many people looking for that "middle ground" that I basically built the whole app around it. Glad it resonates!
You'll do better showing this to the people who would be your users. Looks like a solid idea to make some money on the side solving a problem you actually have.
A lot of people on HN wouldn't be your users. That's fine. Find them and post this there.
> AI-generated artifacts (like "smart quotes" or em-dashes)
I write from the keyboard using “smart quotes…” It’s so much more beautiful.
Smart quotes should work like ligatures rather than being special characters.
Totally agree for prose. The headache is that AI often generates code with those smart quotes, which causes immediate syntax errors in compilers.
That’s why I made it a toggleable rule: keep them for writing, but swap them automatically when you need valid code.
Wish this were built into the OS! Love the idea
The movies on the Features page don't play on Firefox: https://custompaste.com/#features
Love the idea, would be very interested in a version for MacOS
Thanks! Right now it's Windows only because it hooks deep into the system to handle the formatting and transformation properly, which is totally different on Mac.
However, a macOS version is the #1 request I get. It is definitely on the roadmap! If you want, you can drop your email in the form at the very bottom of the site (under "Don't Miss What's Next") and I'll notify you specifically when the MacOS version is ready.
Nitpick: It’s macOS, lowercase m.
I've been working on something super similar. https://github.com/paulirish/markpaste
There's now a CLI that'll read and update your (Mac) clipboard with the result. For this italic use case you'll have to edit the source but it won't be that bad.