All ideas
1

Cloud share links with expiry

Under considerationDGgdarko16 August 2026

Summary

Share a screenshot or a recording with a link, without running your own storage. Upload from Snim, get a snim.dev link on your clipboard, and let it stop working after a while. For captures that should not outlive the conversation. This idea is still under consideration, so the details below may change.

What you will be able to do

  • Pick Snim Cloud as an upload destination and upload in one click, with the share link landing on your clipboard.
  • Let links expire after 30 days by default, or choose a shorter time.
  • Send a clean share page that shows the image or plays the video, with a download button. Links show a preview when pasted into chat apps.
  • Manage your uploads on snim.dev: copy a link, change when it expires, or delete a file at any time.
  • Later: serve share links from your own domain, such as shots.example.com.

How it works

  • Uploads belong to your snim.dev account, so you sign in with GitHub or email. You connect the app once with a personal upload token that you create, and can revoke, on snim.dev.
  • Share links use long random addresses that cannot be guessed or listed.
  • Snim Cloud accepts what Snim makes: PNG, JPEG, WebP and GIF images, and MP4 recordings.
  • Expired and deleted files are removed for good.
  • Your own S3, SFTP and FTP destinations stay exactly as they are, next to Snim Cloud.

Platforms

  • Windows: The same Snim Cloud destination as everywhere.
  • macOS: The same Snim Cloud destination as everywhere.
  • Linux: The same Snim Cloud destination as everywhere, including the Flatpak.

Not in this version

  • No anonymous uploads: every upload belongs to an account.
  • No team accounts or shared folders.
  • Share links on your own domain come after the first version.

Status

  • Share pages, expiry and upload management on snim.dev
  • Snim Cloud destination in the desktop app
  • Share links on your own domain

0 comments

No comments yet. Say why this matters to you.

Sign in with GitHub to join the conversation.

Sign in with GitHub