Thank you Andreas for investing the time to enhance the Clipboard Manager. Even with all of BTT’s powerful functionality, I consistently rely on the Clipboard Manager the most.
After using the updated version for over two weeks, I’ve found that having direct access to the pasteboard’s UTIs is incredibly valuable. However, the experience still feels somewhat cumbersome in practice. I’d like to provide some constructive feedback to help you determine what changes could best improve this already excellent feature.
UX Suggestion
Currently, when viewing a clipboard item, the default selection is “Auto.” I suggest removing the “Auto” option and instead always displaying the actual automatically selected UTI. This would provide immediate clarity on which UTI is active without requiring extra steps. I believe this small change could streamline the user experience and help users more intuitively understand what they’re viewing.
Unexpected Behavior / Bug Report
When viewing a clipboard item as public.html, choosing “Rendered” correctly shows styled, bold-red text. However, switching to “Raw Text” still applies styling instead of showing the underlying HTML code as plain text. This is unexpected. In “Raw Text” mode, the HTML should appear as literal markup, with no formatting applied.
Additional UX Improvement for Complex Formats
Some UTIs—like com.apple.notes.richtext—are encoded as binary plists. It would be extremely helpful if these binary plist formats could be viewed in a more readable form. For example, using /usr/bin/plutil
or /usr/libexec/PlistBuddy
to parse and format the data (e.g. plutil -convert xml1
, plutil -p
, or PlistBuddy -c "Print"
) would make it much easier to understand the data.
Ideally, these parsing options could be integrated into the “Rendered” dropdown, allowing users to select more meaningful representations for binary plist data and other complex formats. Even better, consider letting users define these “Rendered” options from “Reusable Named Triggers” in BTT. This approach would keep things simple for those who don’t need advanced UTI features, while giving power users the flexibility to customize and extend their rendering capabilities—covering a wide range of data types without causing information overload.
Additional UX Suggestion for Hex View
Currently, the “HEX” option shows only a raw hex string. A more valuable layout—similar to what Hex Fiend and the open-source Pasteboard-Viewer app provide—would display hex values on the left and their ASCII representations on the right. This side-by-side view helps users quickly identify readable text, understand data structures, and troubleshoot issues.
Pasteboard-Viewer achieves this by using Hex Fiend’s SDK. If BTT integrated Hex Fiend’s SDK, it could immediately leverage a proven, user-friendly implementation, saving development time and providing a familiar, high-quality hex viewing experience.
Thank you again for all your hard work!