Contact anyscan.download

Email

Write to [email protected]. It reaches the person who maintains the site. Messages are read in English.

What is useful in a bug report

A code that will not scan, a spreadsheet that imports incorrectly or a label that prints at the wrong size can almost always be tracked down from a few details:

• Which tool you were using — Create, Batch, Scan, Labels or Validate.
• The symbology involved, such as QR, Code 128, EAN-13 or GS1-128.
• The shape of the input rather than the input itself — for example “a 13-digit number beginning with 40” or “a CSV with two columns and a header row”.
• Your browser and version, and whether you are on a phone, tablet or desktop.
• What you expected to happen, and what happened instead.
• For printing problems: the paper or label size, the DPI, and whether the output came from the PDF or the ZPL export.

Please do not send confidential data

anyscan.download is built so that the values you encode never leave your browser, and email would defeat that. Do not paste Wi-Fi passwords, customer records, unreleased product numbers, personal contact cards or anything else confidential into a message. A description of the input's shape is enough to reproduce nearly every defect, and where it is not, a small synthetic example that shows the same behaviour works just as well.

Specific topics

• Standards corrections. If the tool disagrees with a published specification — a check digit, a GS1 application identifier, a ZPL command or a label template's dimensions — say which specification and which clause, and it will be checked against the source.
• Accessibility. Problems with keyboard navigation, screen-reader output, contrast or touch targets are treated as defects, not enhancements.
• Privacy. Questions about the local-processing boundary, or a report that something appears to contradict it, are taken seriously. The privacy page describes how to audit the boundary yourself.
• Advertising. Concerns about an ad placement, including an ad that appears somewhere it should not, can be reported to the same address.

What this tool cannot help with

anyscan.download encodes identifiers you already hold; it does not issue them. Requests for GS1 company prefixes, GTINs, ISBNs or other registered numbers have to go to the relevant issuing organisation. Likewise, whether a particular code scans on a particular piece of hardware ultimately depends on that printer and that scanner, which cannot be tested from a browser — the verification methodology explains where the local check stops.