All resources

Long-form guide

DrawShot for Teams

10-page guide for IT admins and team leads evaluating DrawShot for fleet deployment.

Render the source to PDF — instructions in the markdown file header

A practical guide for IT admins, security leads, and engineering managers evaluating DrawShot for fleet deployment.

By Shraddha Mittal · drawshot.dev · v1.0

Executive summary

What DrawShot is: a free, native macOS screenshot and annotation tool built around fast time-to-clipboard. Captures, annotations, and saves are local-only — no telemetry, no cloud, no account.

What it isn't: a team collaboration platform. There's no shared workspace, no cloud library, no centralized administration console. DrawShot stops at "image in clipboard"; your existing tools (Slack, Linear, GitHub, Jira) handle distribution.

Why it might fit your team:

  • Free to deploy at any scale. No per-seat licensing.
  • Local-only privacy posture simplifies security review.
  • Single network domain (updates.drawshot.dev) — easy to allowlist or block.
  • Standard macOS app: notarized, sandboxed, deployable via MDM.

Why it might not:

  • No central admin or fleet-wide configuration today.
  • No telemetry means I can't tell you how your team uses it.
  • macOS-only.

Security review

For your security team, here's what they'll want to know.

Code signing and notarization

  • Bundle ID: dev.drawshot.app
  • Developer ID: Shraddha Mittal (individual developer)
  • Notarization: signed and notarized by Apple. Verified via spctl --assess --type exec /Applications/DrawShot.app.
  • Distribution: direct download via drawshot.dev. Not in the Mac App Store today.

Permissions requested

Permission Purpose Required?
Screen Recording Read pixels in user-selected region Yes
Accessibility Global hotkey for capture Optional
Notifications Capture-complete notifications Optional

DrawShot does not request: Files & Folders, Camera, Microphone, Contacts, Calendar, Location, Photos, Reminders, or any other macOS privacy-protected scope.

Network egress

Single egress domain: updates.drawshot.dev (HTTPS only, Cloudflare-fronted).

Request shape (once per day, optional):

GET https://updates.drawshot.dev/v1/check
Headers: User-Agent: DrawShot/1.0 (macOS 14; arm64)

Request body contains:

  • App version
  • macOS major version
  • CPU architecture

Request body does not contain: user ID, machine ID, hardware serial, MAC address, IP, telemetry, or any user-generated content.

To fully air-gap: block updates.drawshot.dev at the firewall. App continues to function.

Data handling

  • Captures stay on the user's Mac. No upload, no sync.
  • Local storage paths:
    • ~/Library/Application Support/DrawShot/sessions/ — per-capture session data
    • ~/Pictures/DrawShot/ — saved captures (only created on ⌘S)
    • ~/Library/Preferences/dev.drawshot.app.plist — user preferences
  • No log files in ~/Library/Logs/.
  • No data shared between users.

Crash reporting

DrawShot does not integrate Sentry, Crashlytics, or any third-party crash reporter. macOS crash reports are written to ~/Library/Logs/DiagnosticReports/ like any other app, and stay on the user's Mac.

If a user wants to send me a crash log, they do so manually.

Source availability for audit

DrawShot is not open-source today. If your security team requires source inspection before approving deployment, use the contact form at drawshot.dev/contact. I can arrange a read-only repo invitation under NDA.

Deployment

Manual install (per machine)

  1. User downloads .dmg from drawshot.dev.
  2. Drag DrawShot.app to /Applications/.
  3. Launch, accept Gatekeeper prompt.
  4. Grant Screen Recording permission via System Settings.

MDM deployment

Standard macOS app — deploys via Jamf, Mosyle, Kandji, Addigy, etc.

Suggested deployment plan:

  1. Distribute DrawShot.app via your MDM's app distribution mechanism.
  2. Pre-grant Screen Recording via a PPPC (Privacy Preferences Policy Control) profile.
  3. Optionally pre-seed preferences via a Configuration Profile targeting ~/Library/Preferences/dev.drawshot.app.plist.

Pre-seeding preferences

The preferences plist supports the following keys (subset):

Key Type Effect
HotkeyRegionCapture String Custom hotkey for region capture
SaveLocation String (path) Default save folder
CheckForUpdates Bool Enable/disable update check
SessionRetentionHours Int Hours to keep dismissed sessions (default 24)
DefaultColorIndex Int (0-5) Default annotation color

Full reference available on request — use the contact form at drawshot.dev/contact.

Uninstall

Drag DrawShot.app from /Applications/ to Trash. To fully remove user data:

  • ~/Library/Application Support/DrawShot/
  • ~/Library/Preferences/dev.drawshot.app.plist
  • ~/Pictures/DrawShot/ (only if user has used ⌘S to save captures)

Use cases by team

Engineering teams

Bug reports with annotated repros. Single-key annotation workflow makes the friction low enough that engineers actually annotate their bug screenshots, instead of attaching naked captures that require triage clarification.

In a measurement I ran with one beta team: bug-triage clarification requests dropped by ~30% after standardizing on DrawShot for repro screenshots.

Design teams

Design review feedback that references both Figma frames and external context (competitor screenshots, working products, references). DrawShot bridges between in-Figma critique and out-of-Figma examples.

QA / testing teams

Multi-step bug repros with step markers. Customer-data redaction via the blur tool. Side-by-side regression captures. See the QA workflow post for patterns.

Product / project managers

Annotated screenshots in roadmap docs, status updates, customer feedback summaries. Most teams use Notion or Linear for these; DrawShot is the on-ramp.

Customer support teams

Screenshots from screen shares with customers, annotated and pasted into ticket replies. Blur tool for PII protection. Speeds the response loop significantly.

Pricing

Free for everyone, including commercial use, for any team size.

There's no per-seat fee, no team license, no enterprise tier. The same app on a personal Mac and a managed fleet of 200 Macs costs $0.

A Pro tier is planned for late 2026 — opt-in, individual subscription (~$4/month), adds new features that do not exist in 1.0. Nothing in the free tier today will be paywalled later.

If your team finds DrawShot useful and wants to support continued development, the right path is to encourage individuals on your team to subscribe to Pro once it launches. No enterprise procurement, no separate invoice.

What DrawShot doesn't do

A short and honest list:

  • No central admin console. I can't help you see "who's using DrawShot" or push fleet-wide settings beyond what MDM profiles can do.
  • No cloud library. Captures stay on each user's Mac.
  • No team activity feed. Captures don't aggregate anywhere.
  • No SSO / SCIM. No account = no SSO.
  • No usage analytics. I can't give you adoption metrics.
  • No SLA, formally. I'm one designer with a day job. Email response time is typically <48 hours, but it's not contractually guaranteed.
  • No Linux or Windows version. macOS-only.

If any of these are dealbreakers for your team, DrawShot probably isn't the right fit, and that's fine. A paid capture cloud, Droplr, or Markup.io will serve those needs better.

Comparison to other team capture tools

DrawShot Paid capture cloud Droplr
Per-seat cost Free ~$8/user/mo ~$7/user/mo
Cloud sharing None Yes Yes
Team admin console None Yes Yes
Telemetry None Default on Default on
Self-host option N/A (no cloud) No No
Source for audit Under NDA No No

DrawShot is the cheaper, simpler option if your team doesn't need cloud sharing. If you do, look at the leading paid capture cloud — it's well-built and worth the price.

FAQ

Will pricing stay free?

The free tier as it exists in 1.0 stays free. Pro adds new features for opt-in subscribers; it doesn't remove anything from free.

What happens if you stop developing DrawShot?

Honest answer: I'm one person. If I stopped maintaining it, the app would continue to work as it does today on supported macOS versions — but bug fixes and new features would stop.

To mitigate: I've committed to maintaining the app through at least macOS 16 (assuming Apple releases one in 2027). If I had to stop, I'd give 6 months' notice and consider open-sourcing the codebase so the community could take over.

Can we get a paid support agreement?

Today, no. If your team's deployment is significant (50+ seats) and you want a direct line, use the contact form at drawshot.dev/contact — I'm open to informal agreements.

Will you build a team tier with cloud features?

Not on the roadmap. The team-collaboration market is well-served by other tools, and DrawShot's value is the local-first posture. Adding cloud changes the product identity.

Can we white-label / OEM DrawShot?

Not a path I'm pursuing.

Getting started

For a team pilot:

  1. Try it yourself first. Install DrawShot on your own Mac, use it for a week. See if the workflow feels right.
  2. Identify 3-5 power users. Engineers who file bug reports, designers who do reviews, QA folks. Have them install and adopt for two weeks.
  3. Standardize on annotation conventions. Pick team colors (red for "wrong," green for "right"). Build muscle memory.
  4. Decide on fleet deployment. If the pilot works, deploy via MDM with the suggested PPPC profile.

If you want help with any of this, use the contact form at drawshot.dev/contact. I'm happy to talk through your specific setup.

Contact

For general inquiries, security review requests, or feedback — use the contact form at drawshot.dev/contact. Reach Shraddha directly via the LinkedIn profile linked from the website footer.

drawshot.dev · v1.0 · macOS 13+ · free