I built Lumshot, a modern screenshot and visual communication tool for Windows
Hi everyone,
I'm excited to finally share Lumshot, a project I've been working on for quite some time.
The idea came from a simple frustration. I use screenshots every day to report bugs, review designs, explain ideas, and communicate with clients and teammates. Most screenshot tools do a great job of capturing the screen, but they don't help much after that.
I wanted a tool that made the entire workflow smoother, so I started building Lumshot.
Today it includes:
Fast screenshot capture
Powerful annotation tools
OCR text extraction
Smart redaction
AI Auto Paste for faster AI workflows
Create Jira issues without leaving Lumshot
Lumshot is currently free during beta because I want to learn from real users before introducing the paid version. Every bug report, feature request, and piece of feedback helps shape what comes next.
If screenshots are part of your daily workflow, I'd genuinely love to hear what you think. What is one thing you wish your current screenshot tool did better?
You can try Lumshot here:
https://lumshot.app
Thanks for taking the time to check it out. I appreciate any feedback, whether it's about the product, the design, or the overall experience.
Windows is a crowded shelf for this — Snipping Tool ships free, ShareX is free and does nearly everything, and Lightshot has inertia. So the interesting question isn't features, it's which of those you're actually taking users from.
"Visual communication" in the tagline suggests the wedge is after the capture rather than the capture itself. Is that where the product's weight sits — annotation, sharing, the link you send someone — with the screenshot part being table stakes? If so I'd expect that to be the harder thing to get right anyway, since capture is a solved problem and handoff isn't.
That's exactly how I see it. Screenshot capture itself is mostly solved. I'm not trying to replace it with another capture button. The focus of Lumshot is everything that happens after the screenshot: explaining, collaborating, creating Jira issues, or sending it to AI tools with fewer steps. That's the workflow I'm trying to improve.
That's a cleaner position than competing on capture, and it's the half that's genuinely unsolved. Everyone can take the screenshot; almost nobody can get from the screenshot to a filed issue without three context switches.
The Jira path is the one I'd want to understand first. Filing an issue needs fields a screenshot can't know — project, component, priority, who it's assigned to. Does it ask, remember per project, or try to infer from what's in the image? Asking is honest but it's another form to fill in, which is exactly the friction you're removing. Inferring is faster and wrong sometimes, and a wrong-project ticket is arguably worse than no ticket.
Curious where you landed, because that decision probably defines whether this replaces the workflow or just shortens it.
The Jira integration is probably more valuable than the screenshot features themselves. Capturing an issue is easy; turning that capture into something actionable is where teams lose time.
The interesting direction is whether Lumshot becomes a communication workflow tool rather than just a capture tool.
I completely agree. That's exactly the direction I'm aiming for. The screenshot is just the starting point. We're also working on integrations with Trello, Linear, and other tools to make the workflow even smoother
That makes sense. I'm curious whether that direction came mainly from your original vision for Lumshot, or whether users were already trying to push screenshots into those workflows themselves.