Share through your own storage.

Prepare a destination.

You need an S3-compatible service, a bucket and credentials authorized for the operations you intend to use. Check your storage provider's permissions, URL format, region and charges.

Connect the app.

• Open the upload settings and enter your endpoint, region, bucket and credentials.
• Choose the link behavior appropriate for your bucket.
• Use the connection test before uploading an image. The test checks bucket access without sending screenshot pixels.
• Start an upload explicitly from the editor or preview.

Understand the link.

A public object URL follows your bucket's access policy. A temporary signed link may grant access until it expires. Treat either kind of sharing link according to the access it provides; do not assume a difficult-to-guess URL makes an image private.

Keep credentials local.

Configuration is stored in Windows Credential Manager. Klips signs requests locally and sends uploads directly to your chosen provider, without routing credentials or images through a Klips server.

Manage an upload.

The app keeps a local history of uploads, including link and expiry information. Removing a local history entry is different from deleting the corresponding remote object. Use the intended remote-delete action and check the result.

If an upload fails.

Check the endpoint, region, bucket permissions and system clock. Avoid putting credentials or a complete signed link into a support message. A failed connection test does not require you to send a screenshot.