PictobankSupport
Contact

Contact

Send Pictobank a tracked message about account access, billing, Storage+, Local Processing, sharing, or processing tools.

Contact support

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.

View P.A.R.Q.
PICTOBANK
HomeContact

Contact

Contact Pictobank Support

Reach Pictobank for support, billing, Local Processing, Storage+, privacy, sharing, abuse, or account questions.

Contact routes

Choose the fastest support path

The public form is best for tracked requests. Email is useful when you already have a ticket thread.

Support email

Email support@pictobank.io. Include account email, ticket ID, checkout session, or share link only when relevant.

Contact form

The Support page creates a ticket and works for signed-in and signed-out users.

Privacy context

For private or sensitive workflows, describe the issue without including file contents.

Use it when

Example decisions

Small practical examples to help choose the right workflow.

Billing issues

For billing issues, include the email used at checkout.

Upload problems

For upload problems, include file type and approximate size.

Sensitive files

Describe the issue without pasting private file contents into the message.

Plain-language legend

Quick terms

Short definitions for terms used on this page.

Support ticketA tracked support request.

Why it matters: It gives support context and a reference trail.

Example: Include a ticket ID when replying about the same issue.

CategoryThe topic selected for a support request.

Why it matters: It helps route the ticket to the right context.

Example: Choose billing for subscription or invoice questions.

Checkout emailThe email used during payment or purchase.

Why it matters: It helps locate billing and license records.

Example: Use the checkout email when asking about license recovery.

License recoveryA support flow for finding or restoring paid Local Processing access.

Why it matters: It depends on purchaser email and license records.

Example: Ask for recovery using the email used at checkout.

Billing issueA problem with checkout, invoice, subscription, or payment state.

Why it matters: Billing context is handled through Stripe and Pictobank access records.

Example: Include the checkout email and approximate charge date.

Upload failureA file upload that does not complete or cannot enter a workflow.

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.

Share linkA link that can open selected shared files while active.

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.

Storage+An account-based subscription for saved exports and organization.

Why it matters: It changes whether cloud exports persist until deleted or expired.

Example: Use Storage+ when you want saved folders and reusable exports.

Local ProcessingA device-first paid mode for heavy private repeat work.

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.

Before you contact support

Short answers that help keep support requests useful without exposing private file contents.

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.