Contact

Write to hello@screenshot2text.com.

Please include:

• The page URL you are writing about (for example /, /pdf-to-text, /guides/better-screenshot-ocr, or /privacy).
• A short description of what you need or what looked wrong.
• Your browser and device type if the issue is about recognition, layout, or ads (Chrome on Windows, Safari on iPhone, and so on).

Keep the message short. A few clear sentences beat a long dump of logs.

Someone on the Tiny Utility Lab side reads the inbox. This is a small independent utility, not a staffed help desk with overnight coverage. Messages are not auto-replied by a bot that pretends to be support.

We reply when we can. Typical turnaround is a few business days. Some weeks are faster. Some weeks take longer if travel, other product work, or a flood of similar questions piles up. If you have not heard back after about a week, it is fine to send a short follow-up with the same subject line. Please do not send the same request to multiple addresses. There is only one contact mailbox.

We do not offer phone support, live chat, or social DM support for product questions. Email keeps a written record and keeps private details out of public threads.

You can expect a human reply for:

• Product questions about how Screenshot2Text works.
• Privacy or policy questions that need clarification beyond the published pages.
• Guide corrections, broken links, or clear copy mistakes.
• Accessibility notes and honest feedback about the UI.
• Ad placement reports when an ad breaks the page or covers the drop zone.

You should not expect:

• Instant replies around the clock.
• Custom OCR tuning for one file.
• Guarantees about accuracy on a specific screenshot you describe in words.
• Feature commits with dates.
• Help recovering text from a closed browser tab. Recognition runs on your device. We never held your file, so we cannot look it up.

If the answer already lives on the site, we may point you there instead of rewriting the same explanation in email.

Please do not attach screenshots, photos, PDFs, or archives to contact mail.

There are three reasons:

1. Privacy. The whole point of Screenshot2Text is that recognition stays in your browser. Emailing us the file creates a copy we never asked for.
2. We cannot re-run your job remotely. There is no server-side queue where we open your attachment and push text back. Even if we looked at the picture, that would not fix your local tab.
3. Inbox safety. Attachments from strangers are a poor default for a small operator inbox.

If recognition looks wrong, describe what you see (dark UI, tiny font, multi-column layout, wrong language selected). First, try the guides on how to fix wrong or messy OCR text and how to take a screenshot that OCR reads well. For privacy questions, read Privacy before writing. For who builds the tool, see About.

• Clarifying how in-browser OCR differs from upload converters.
• Pointing you to the right tool page (/, /pdf-to-text, /image-to-text-no-upload, and related landings).
• Confirming that the product is free to use, with no paid plans or account wall for basic OCR.
• Fixing factual errors on About, Contact, Guides, Privacy, or Terms.
• Hearing about browsers where the reader fails to start, language packs that never load, or PDF pages that never render.
• Notes when AdSense units collide with the drop zone or the copy box on a specific viewport size.

• Reading a file for you and emailing back the text.
• Recovering work from a tab you already closed or a device you no longer have.
• Legal advice, compliance certifications, or enterprise SLAs.
• Helping with content you are not allowed to copy, or building custom hosted APIs and on-prem installs on demand.
• Refunds or billing questions. There are no paid plans.
• Changing Google AdSense inventory on a per-user basis. Ad personalization and cookie controls are documented on Privacy.

• About: who runs Screenshot2Text / SnapOCR under Tiny Utility Lab, why OCR stays local, honest limits.
• Guides: practical how-tos for cleaner results, private browser OCR, scanned PDFs, and failure modes.
• Privacy: cookies, CDN fetches for engine files, hosting logs, and how ads are separate from recognition.
• Terms: acceptable use and accuracy limits.
• Homepage converter: drop an image or PDF and run OCR in your tab without creating an account.

Screenshot2Text is free to use. Recognition does not run on our servers. If email is still the right next step after those pages, hello@screenshot2text.com is the address.