ScannerBench
See the text and key events your keyboard scanner sends. Compare them with the value you expected.
Test a scannerFREE KEYBOARD-SCANNER CHECKS
See the extra character that breaks the match.
Spaces, prefixes, terminator keys and invisible characters can be easy to miss. Inspect the captured value and test an explicit comparison rule without losing the original.
Free to use. No account. Your working data stays in your browser.
INPUT / INSPECTOR EXAMPLE
Expected value
000017
Observed value
000017␠
One extra character
U+0020SPACEPosition 7
An illustrative value, not a device result.
MADE FOR THE FLOOR
For developers and support teams matching scanner input to order numbers, location codes or known test payloads.
A USEFUL STARTING POINT
Keep exact comparison visible
An exact mismatch is evidence. ScannerBench shows it even when a configured comparison rule produces a match. You can remove a literal prefix or suffix, trim outer ASCII spaces or convert CRLF to LF in the comparison view. Rules apply in the order you select, only to the selected observation.
FROM QUESTION TO EVIDENCE
Three steps to a useful result.
- 01
Capture a known value
Start with a barcode whose encoded text is independently known. Inspect the escaped text and Unicode character list before adding any transformation.
- 02
Distinguish text from keys
Look at received characters and the event log separately. Enter and Tab may finish capture without becoming text. A Ctrl+] event alone does not establish that U+001D reached the field.
- 03
Try one explicit rule
Add only the rule you want to investigate. Compare the original exact result and the configured result, then include the observation in a reviewed report.
A trailing space is still a character
The strings ABC-0017 and ABC-0017 followed by U+0020 are different. An outer-space rule can demonstrate that the space explains a mismatch, while the original capture remains unchanged. This does not change the scanner or fix the receiving application.
BEFORE YOU START
A few practical answers.
Can it show a GS separator?
If the browser field receives U+001D, the inspector names it as GS. Literal backslash-u text is a different value. The current tool does not parse or validate GS1 element strings.
Are CR and LF preserved exactly?
Browser textareas normalize line endings. Available paste-event text is retained separately from field text, and imported expectations retain their strings. Choose the observation carefully when comparing line endings.
Will my next scan be silently corrected?
No. Comparison rules do not rewrite stored captures or program the scanner. Exact and configured outcomes stay separate.
What are the current limits?
This is a software-tested alpha. Physical scanner and OS combinations are not yet qualified. Model selection provides reviewed manual references; it does not detect, configure or certify a scanner. Raw HID, serial input, camera scanning, barcode decoding and GS1 interpretation are outside this release.
What happens to my data?
Scan values, expectations and device notes are processed in browser memory. No account, upload or tracking scripts are required. Reloading loses the session. Reports are redacted by default and downloaded only after review. Hosting may log ordinary page requests; suite links contain only a fixed referral marker.
ONE SMALL JOB, DONE WELL
Put ScannerBench to work.
Open the free tool and start with one known example.
THE SMARTFACT WORKBENCH
Small tools. Useful on their own.
Better on the same workbench.
Check the input, check the print, then make something useful. Choose the tool for the job in front of you.
PrintBench
Print a known PDF, measure its reference marks and compare scans from the printed codes.
Check a printFactoryCards
Create 100 × 50 mm bin and rack cards with Code 128 or QR, from one record or a CSV.
Make bin cardsSmartFACT Labels
Explore controlled production labelling, with label rules, reviewed output and print history.
Explore Labels