My link doesn't open
The upload worked, but the link shows an error. The bucket is usually private, or the link address is off.
On this page
If Test connection says Connected and uploads work, but the link shows an error, the problem is between your bucket and the web. There are two usual causes.
1. The bucket isn't readable by link#
Uploading needs your key. Opening a link doesn't, so the files have to be readable by anyone who has the address.
Cloudflare R2: in the bucket's Settings, check Public access. Either the r2.dev address is enabled, or a custom domain is connected. See set up Cloudflare R2.
Amazon S3: the bucket needs the public-read policy, and Block public access must allow it. See set up Amazon S3.
Backblaze B2: the bucket's files must be set to Public.
2. The link address is off#
A share link is your link address plus the file's name. If the address is wrong, every link is wrong.
In your provider's dashboard, find a file VizShot uploaded. It's named like
2026/10/and a long string of letters and numbers, ending in.png.Open that file's public address, in whatever way your provider offers.
Compare it to a link VizShot gave you. Everything before
2026/10/is what belongs in your link address.
Common slips:
A missing part. Backblaze's friendly address includes
/file/your-bucket. Leave that out, and it fails.The wrong address for the bucket. Using the address for a different bucket, or an old one.
A domain that isn't connected yet. A custom domain can take a few minutes to start working.
Old links#
Links already shared keep the address they had when they were made. If you change the link address later, only new uploads use the new one.
Check from another browser#
Open the link in a private window, or on your phone using mobile data. If it opens there but not for someone else, it's likely the other person's network or the link got cut off when it was pasted.
Still stuck? Contact support with your provider's name, and the link address you've set, but not your keys.