Browse documentation

Uploading to S3

Savvyshot can upload the screenshot you're editing straight to your own S3 bucket and hand you back a shareable link. Nothing is routed through a Savvyshot server — the request goes from your machine directly to the endpoint you configure, using credentials that stay on your machine.

This works with Amazon S3 and with any S3-compatible storage: Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi, MinIO, and similar.

S3 upload requires an activated license. On an unlicensed (free) copy the Upload button is disabled and the S3 settings can't be opened. See Plans & Pricing and Activating Your License.

Setting up a bucket

  1. Activate your license if you haven't already — the settings below are locked until you do.
  2. Open Settings → S3 Upload and choose Set up. (You can also use Set up S3 upload… in the editor's Upload menu.)
  3. Fill in the fields below.
  4. Choose Test connection. Savvyshot writes a tiny probe object to the bucket and removes it again, so you find out about a wrong key or a missing permission before you need the feature.
  5. Choose Save.

You can save more than one bucket — use Add to create another, and pick which one the Upload button uses with Use as default for the Upload button.

Configuration reference

FieldDescription
NameLabel shown in the editor's Upload menu, e.g. "Work bucket". Optional — the bucket name is used if you leave it empty.
EndpointThe service endpoint, e.g. https://s3.us-east-1.amazonaws.com or https://<account>.r2.cloudflarestorage.com. Leave it empty for Amazon S3 and Savvyshot derives it from the region.
RegionThe bucket's region, e.g. us-east-1. Cloudflare R2 uses auto. Part of the request signature, so it has to match the bucket.
BucketThe bucket name.
Access key IDThe access key of the user or token allowed to write to the bucket.
Secret access keyThe matching secret key. Stored encrypted (Keychain on macOS, DPAPI-backed storage on Windows) and only ever sent to the endpoint above.
Folder prefixOptional folder the screenshots are written into, e.g. screenshots/. Supports the {date}, {year} and {month} placeholders, so screenshots/{year}/{month} sorts uploads into dated folders.
Public base URLOptional. A CDN or custom domain in front of the bucket, e.g. https://cdn.example.com. The returned link is built from this instead of the bucket endpoint.
Make uploaded files public (public-read ACL)Sends the public-read ACL with the upload. Only works on buckets that still allow ACLs — see Getting a link that actually works.
Use path-style URLsAddresses the bucket as https://host/bucket/key instead of https://bucket.host/key. Required by MinIO and some self-hosted gateways.
Use as default for the Upload buttonMakes this the bucket the Upload button uploads to.

Licensing note

S3 upload is unlocked by activating a Basic or Pro license. Without one, the editor's Upload button is disabled and Settings → S3 Upload offers a Buy License link instead of the configuration form. Buckets you configured while licensed are kept if a license later lapses — they become usable again as soon as it is reactivated.

Uploading a screenshot

  1. Edit and style your screenshot as usual.
  2. Choose Upload in the editor's footer. The screenshot is rendered exactly as it would be exported, then uploaded to your default bucket.
  3. To upload to a different saved bucket, open the Upload menu and pick it from the list.
  4. When the upload finishes, the link is copied to your clipboard and shown in a dialog with Copy link and Open link buttons.

Uploads are named using the same screenshot filename template as saved files (see Settings), so Savvyshot_{datetime} becomes Savvyshot_2026-09-20_14-32-08.png — with the folder prefix in front of it. Uploads are PNG.

Screenshots with a video background can't be uploaded; export them as GIF or MP4 instead (see Exporting).

Permissions the credentials need

The upload itself needs only s3:PutObject on the objects under your folder prefix. Test connection also tries s3:DeleteObject to clean up its probe object — if delete isn't allowed, the test still passes and a single tiny .savvyshot-connection-test object is left in the bucket.

A minimal IAM policy for Amazon S3:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:PutObject", "s3:DeleteObject"],
      "Resource": "arn:aws:s3:::my-screenshots/screenshots/*"
    }
  ]
}

Prefer a dedicated key scoped to this one bucket over a key that can reach the rest of your account.

The link Savvyshot returns points at the object. Whether other people can open it depends on your bucket, not on Savvyshot:

  • Amazon S3 buckets created since April 2023 have ACLs disabled, so Make uploaded files public is rejected. Make the prefix readable with a bucket policy, or put CloudFront in front of the bucket and set Public base URL to the CloudFront domain.
  • Cloudflare R2 ignores ACLs entirely. Enable the bucket's public r2.dev domain or attach a custom domain, then set Public base URL to it.
  • MinIO / self-hosted: set a read-only anonymous policy on the prefix, and tick Use path-style URLs.
  • Buckets that are private by design still work fine — the link just needs a signed URL or console access to open. The upload itself is unaffected.

Troubleshooting

MessageWhat it usually means
SignatureDoesNotMatchThe secret key or the Region is wrong. Both are part of the request signature.
AccessDenied / HTTP 403The key can't write to this prefix, or the bucket policy blocks it. Check the policy against the prefix you configured.
NoSuchBucket / HTTP 404Bucket name or endpoint is wrong, or the service needs Use path-style URLs.
InvalidAccessKeyIdThe access key ID doesn't exist on that endpoint — a common symptom of pointing AWS credentials at a non-AWS endpoint, or vice versa.
AccessControlListNotSupportedThe bucket has ACLs disabled. Untick Make uploaded files public and use a bucket policy or CDN instead.
Could not reach <host>The endpoint is unreachable: check the URL, and check the port for a self-hosted endpoint.

Tips

  • Use a folder prefix like screenshots/{year}/{month} so a bucket you upload to daily stays browsable.
  • Put a CDN or custom domain in Public base URL — the link stays stable and short even if you move buckets later.
  • Keep a second configuration pointed at a private bucket for screenshots that shouldn't be shareable, and make the public one your default (or the other way round).

Last updated September 21, 2026