Skip to content
Snappyshot
Sharing & storage

Your captures, your bucket, your bill

Most capture apps hand you a link and keep the file. Snappyshot hands you a link to a file in storage you already own — and works perfectly well with no cloud storage at all.

Get SnappyshotEvery sharing feature
  1. 1

    Point it at a bucket

    Open Settings › Sharing and fill in the endpoint, bucket, and region for any S3-compatible host. Press Test connection and Snappyshot uploads and deletes a small file to prove the credentials work.

  2. 2

    Press share on a capture

    The Quick Access overlay shows upload progress and lets you cancel. When it lands, the URL is on your clipboard and the capture is marked as shared in History.

  3. 3

    Manage what you've sent

    Links in the menu bar footer lists everything you have shared, so you can re-copy a URL, open it, or delete the object from the bucket when you’re done with it.

Providers

Anything that speaks the S3 API

Pick a host and Snappyshot's settings look like this. The only setting that trips people up is path-style URLs, so here's which way each provider wants it.

  • Amazon S3Path-style off
  • Cloudflare R2Path-style on
  • Backblaze B2Path-style on
  • DigitalOcean SpacesPath-style off
  • MinIOPath-style on
  • Any S3-compatible hostPath-style on

Running something else entirely? Point Snappyshot at your own upload endpoint instead and tell it which key in the JSON response holds the link.

Settings › Sharing

Connected
Endpointa1b2c3.r2.cloudflarestorage.com
Bucketteam-shots
Regionauto
Folder prefixcaptures/2026/
Public bucket URLhttps://cdn.example.com
Path-style URLs
Access key secret•••••••• in Keychain
Copied to your clipboardhttps://cdn.example.com/captures/2026/9f3a1c7e-deploy-summary.png

No egress fees, and a custom domain in front of the bucket. Test connection uploads and deletes a small file, so a wrong region shows up here instead of mid-share.

Reference

What every setting does

Endpoint, bucket, region
Where captures are uploaded.
Access key and secret
Your credentials. The secret lives in your login keychain, never in a plist.
Folder prefix
A key prefix, so every upload lands in one folder.
Path-style URLs
On for R2, B2, and MinIO. Off for bucket.s3.amazonaws.com.
Link style
A public URL, or a signed URL that stops working when it expires.
Public bucket URL
Serve links from your own domain or CDN instead of the raw endpoint.
Expiry
How long a signed link stays valid.
Upload every capture
Share links without pressing anything.
Security

Three things that matter more than the upload speed

  • The secret never leaves the keychain

    Your access key secret is stored in your login keychain rather than a preferences file, so it isn't sitting in plain text in your home directory.

  • Keys can't be guessed

    Every object key carries a random token. Nobody can increment a number in a URL and land on someone else's capture.

  • Links can stop working

    Choose signed links and set an expiry, and the URL dies on schedule. Local share links support an expiry and an optional password too.

Don’t want a bucket at all?

Leave storage unconfigured and sharing still works. Snappyshot serves the capture from your Mac at its address on the local network, so anyone on the same Wi-Fi can open the link while the app is running. Add an expiry, add a password, and close the laptop when you’re done — the link goes with it.

There’s also a share folder: point it at Dropbox or iCloud Drive and let the service you already pay for do the syncing.

  • No account, no bucket, no configuration
  • Link is scoped to your local network
  • Optional password and expiry per link
  • Stops serving when Snappyshot quits

Your next screenshot could be a lot better.

Build it once, keep it in the menu bar, and stop thinking about where your captures went.

Get Snappyshot for MacRead the source

macOS 14 Sonoma or later · No account · No subscription