For billing issues, include the email used at checkout.
Contact Pictobank support
Send account, billing, sharing, Vault, Local Processing, or image processing questions here. You do not need a paid account. You can also email support@pictobank.io.
Use the form for compression issues, upload failures, Vault and share page questions, Storage+ billing, account access, or Local Processing license help.
What to include
Include the page or tool used, file type, approximate file size, visible error message, and checkout email for billing or license questions. Avoid pasting private file contents into the message.
Your tickets
Open and recent requests
Sign in to see your recent support tickets here.
Use it when
Example decisions
Small practical examples to help choose the right workflow.
For upload problems, include file type and approximate size.
Describe the issue without pasting private file contents into the message.
Plain-language legend
Quick terms
Short definitions for terms used on this page.
Why it matters: It gives support context and a reference trail.
Example: Include a ticket ID when replying about the same issue.
Why it matters: It helps route the ticket to the right context.
Example: Choose billing for subscription or invoice questions.
Why it matters: It helps locate billing and license records.
Example: Use the checkout email when asking about license recovery.
Why it matters: It depends on purchaser email and license records.
Example: Ask for recovery using the email used at checkout.
Why it matters: Billing context is handled through Stripe and Pictobank access records.
Example: Include the checkout email and approximate charge date.
Why it matters: File type, size, browser, and selected tool help diagnose it.
Example: Report that a 42MB WebP failed during upload in Image Converter.
Why it matters: Anyone with the active link may be able to view or download it.
Example: Send a share link only to intended recipients and delete it when access should end.
Why it matters: It changes whether cloud exports persist until deleted or expired.
Example: Use Storage+ when you want saved folders and reusable exports.
Why it matters: It is separate from cloud Storage+ workflows.
Example: Use Local Processing for large recurring batches on your own device.
P.A.R.Q.
Support request questions
Use these prompts to send enough context while keeping private file contents out of the ticket.
What should I include in a support message?
Include the tool used, file type, approximate size, account or checkout email when relevant, and a short description of what happened.
Do I need a paid account to contact support?
No. You can contact support for free workflows, account questions, billing, privacy, and license recovery.
What email should I use for billing or license help?
Use the email used at checkout whenever possible so billing and license records can be found faster.
Should I include private file contents?
Avoid pasting sensitive file contents. Describe the issue and include file type, size, and workflow context instead.
How do I report an upload or processing error?
Include the file type, approximate size, selected tool, browser, and whether the issue happened during upload, preview, or export.
What should I include for share-link issues?
Include the share link or token only when needed, plus what action failed, such as view, download, expiry, or deletion.