Own every screenshot you take.

SFTP / SSH (any Linux VPS, shared hosting with SSH)

• Host — e.g. vps.mysite.com or the IP.
• Port — usually 22.
• Username — the Linux account you SSH in as.
• Password or SSH Key — key auth is safer. Maxisnap supports RSA, Ed25519, and ECDSA keys.
• Remote Dir — where to drop files on the server, e.g. /var/www/html/snaps. The directory must already exist and the user must have write permission.
• URL Prefix — the public URL the file will live at, e.g. https://mysite.com/snaps. Maxisnap appends the filename, so the final share URL is https://mysite.com/snaps/ms_abcd1234.png.

Trip-hazard: if you get a "connection refused" error even though SSH works from your terminal, check that port 22 isn't blocked outbound on your ISP — a couple of corporate networks block it. Port 2222 is a common alternative.

FTP / FTPS (cPanel, shared hosting, legacy hosts)

• Host — ftp.mysite.com.
• Port — 21.
• Username / Password — the FTP credentials your host emailed you. On cPanel, "Main Account" or a dedicated FTP user you create in the FTP Accounts panel.
• Use TLS/SSL — tick this if your host supports FTPS. If you don't know, leave it off. Plain FTP still works.
• Remote Dir — usually public_html/snaps or httpdocs/snaps. Confirm via your host's file manager.
• URL Prefix — where that directory is served from, e.g. https://mysite.com/snaps.

Plain FTP sends passwords in the clear. Use FTPS if your host supports it — and move to SFTP at your earliest chance.

S3 / Cloudflare R2 / any S3-compatible bucket

• Endpoint — your S3 endpoint URL. For Cloudflare R2 this is https://<account-id>.r2.cloudflarestorage.com. For AWS S3 you can leave this blank.
• Region — auto for R2, us-east-1 etc. for AWS.
• Bucket — the bucket name, e.g. my-snaps. It must already exist.
• Key ID / Secret — bucket access credentials with PutObject permission. In R2: R2 → Manage API Tokens → Create Token → Object Read & Write.
• Key Prefix — optional subfolder inside the bucket, e.g. 2026/.
• URL Prefix — the public URL the object resolves at. For R2, you bind a custom domain in the dashboard (e.g. https://cdn.mysite.com).

R2 gives you 10 GB free with no time limit + 1M Class A ops/month — enough for ~10,000 screenshots with room to spare. That's why we recommend it over AWS.

Custom HTTP (your own upload endpoint)

If you've written a tiny upload endpoint on your own backend, point Maxisnap at it:

• Upload URL — your endpoint, e.g. https://api.mysite.com/upload.
• Field Name — the multipart/form-data field the file should arrive on. Most servers expect file.
• Auth Header — e.g. Bearer <your-token>. Stored encrypted in the app's config.
• Response Key — the JSON key in your response that contains the URL to share. If your endpoint returns {"url":"https://..."}, set this to url.

If your endpoint follows the Maxisnap Dashboard contract, the entire dashboard source code is yours to download and self-host — see the Studio Dashboard download in Account settings.