Community
Join the Sealshot Community
Help shape Sealshot as we build it. Share feedback, suggest features, report issues, and tell us how screenshots fit into your workflow.
No account to create and nothing to join — everything below runs on our support inbox and the public GitHub repository.
Ways to take part
Four ways in
Pick whichever matches what you have. None of them needs more than a few sentences to be useful to us.
Share feedback
Tell us what works, what does not, and what would make Sealshot more useful.
Share feedback →Request a feature
Have an idea for a new workflow, capture feature, privacy improvement, search feature, or anything else?
Suggest a feature →Report a bug
Found something broken, inconsistent, or unexpected? Sealshot's Help ▸ Send Feedback… can attach the diagnostics we would otherwise have to ask for.
Report a bug →Test new builds
Try upcoming builds and features and help us catch issues before wider release. Every version ships on GitHub as it lands — watch the repository to hear about them first.
See the latest releases →User research
Tell us how you use screenshots
We'd love to understand how Sealshot fits into different workflows. What field do you work in, what do you use screenshots for, and what is the biggest friction in your current screenshot workflow?
A few examples of the kinds of work people tell us about — a list of starting points, not a list to pick from. If none of them describes what you do, that is the answer we most want to hear.
- Software development
- QA and testing
- Security and IT
- Product and design
- Customer support
- Education and research
- Content and documentation
- Or something else entirely
Roadmap
Help Shape What We Build Next
These are the directions we are already weighing. Which of them matters for your work — and in what order — is genuinely shaped by what people tell us.
- Better screenshot search Finding the capture you half-remember, faster and with less typing.
- Smarter sensitive-data detection Catching more of what should never leave your machine, with fewer false alarms.
- Capture and annotation The everyday path — select, mark up, send — with less friction in it.
- QA and bug-report workflows Getting from "this is broken" to a report a developer can act on.
- Local AI and metadata More understanding of what is in a capture, still entirely on your Mac.
- Organisation and library Keeping thousands of captures navigable instead of merely stored.
None of this is fixed, and the list is not the limit. If the thing you need is not here, that is worth telling us more than agreeing with something that is.
Open source
Sealshot is open source. The app is on GitHub under GPL-3, and what gets built next is decided largely by what people ask for in the issue tracker and in our inbox. There is no roadmap committee here — reading what you send is the process.
One exception: if you have found a security problem, please don't open a public issue. Report it privately instead, as the repository's security policy asks.