Contact WebPKit

Updated 2026-11-17By WebPKit4 min read

The fastest way to reach WebPKit is email: [email protected]. There is no contact form, because a form would require a server or a third-party service and neither is necessary for a static converter. Email is also better for bug reports, since you can paste error text and screenshots of the developer console.

Email is the only channel

The site has no chat widget, no support portal, and no account system. A single mailbox keeps the operation small and avoids collecting data the site does not need. If you write, say what you were trying to do, what happened, and what you expected. Plain text is fine.

Email is not instant. Messages are read in batches, and replies are best-effort rather than a contractual support service. If your question is about how a format behaves, the converter page and the dedicated format pages often answer it faster than a reply would arrive.

What to include in a bug report

A useful report usually contains five things:

  • The browser name and version, and the operating system.
  • The source file's format and approximate dimensions and file size.
  • The output format, quality value, and longest-edge value you selected.
  • The exact message shown in the status line, copied rather than paraphrased.
  • Any error text from the browser console, if you are comfortable opening it.

That is enough to reproduce most problems. A screenshot of the page is helpful when the issue is visual, such as a preview that does not match the downloaded file. Please do not attach the original image unless it is necessary and you are comfortable sharing it; a synthetic test image with the same characteristics is usually better.

What not to send

Do not send passwords, API keys, private client files, or personal photographs. The site does not need them to diagnose a conversion problem, and email is not a secure channel for sensitive material. If a bug only appears with a specific private file, describe its properties: format, dimensions, transparency, and whether it came from a camera, a screenshot tool, or an editor.

Feature requests and scope

WebPKit deliberately does one thing: single-file conversion and resizing in the browser. Batch processing, cloud storage, accounts, cropping, and metadata editing are outside the current scope. Requests for those features are still welcome as context, but they will not change the tool's core constraints. The about page lists the limits and the reasoning behind them. If a feature can be added without a server and without collecting data, it is more likely to be considered.

Corrections to the written content are especially useful. If a page describes format behavior in a way that does not match what you observe, include the page URL and the sentence in question. The goal is for every claim on the site to be verifiable in a browser.

Privacy and security reports

If you believe you have found a way for the site to transmit an image, load an unexpected third-party resource, or expose data it claims not to collect, report it by email with the steps to reproduce. Those reports are treated as priority. The privacy policy describes the intended boundary; a reproducible violation of it is a bug, not a policy debate.

Frequently asked questions

How do I report a conversion bug?

Email the address on this page with the browser name and version, the source format, the chosen output settings, and the exact message you saw; do not attach the file unless asked.

Can WebPKit recover a deleted image or conversion?

No. The site never stores images, so there is nothing to recover or delete on the server.

Do you offer custom image work?

No. WebPKit is a self-service converter only; custom editing, batch jobs, and format migrations are outside its scope.

How fast is the reply?

Replies are best-effort, usually within a few business days; there is no guaranteed support window.

Bottom line

Email [email protected] with a clear description, the settings you used, and the exact error message. Keep private images out of the message. For format questions, check the relevant converter page first - the answer is probably already there.