Support email
Email support@pictobank.io. Include account email, ticket ID, checkout session, or share link only when relevant.
Contact
Send Pictobank a tracked message about account access, billing, Storage+, Local Processing, sharing, or processing tools.
Your message becomes a tracked support request.
Do not include passwords or private file contents.
View P.A.R.Q.Describe private files without including their contents. Add your checkout email only when it is relevant.
Contact
Reach Pictobank for support, billing, Local Processing, Storage+, privacy, sharing, abuse, or account questions.
Contact routes
The public form is best for tracked requests. Email is useful when you already have a ticket thread.
Email support@pictobank.io. Include account email, ticket ID, checkout session, or share link only when relevant.
The Support page creates a ticket and works for signed-in and signed-out users.
For private or sensitive workflows, describe the issue without including file contents.
Use it when
Small practical examples to help choose the right workflow.
For billing issues, include the email used at checkout.
For upload problems, include file type and approximate size.
Describe the issue without pasting private file contents into the message.
Plain-language legend
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.
Short answers that help keep support requests useful without exposing private file contents.
Include the tool used, file type, approximate size, account or checkout email when relevant, and a short description of what happened.
No. You can contact support for free workflows, account questions, billing, privacy, and license recovery.
Use the email used at checkout whenever possible so billing and license records can be found faster.
Avoid pasting sensitive file contents. Describe the issue and include file type, size, and workflow context instead.
Include the file type, approximate size, selected tool, browser, and whether the issue happened during upload, preview, or export.
Include the share link or token only when needed, plus what action failed, such as view, download, expiry, or deletion.