Compliance cases
These are the 7,246 inputs a submission must answer.
A conforming implementation returns true
for the 2,791 valid ones and false
for the 4,455 invalid ones.
You can run the suite without reading it, or open any case to see its input and where its first ill-formed byte is.
Well-formed means Table 3-7 of the Unicode Standard, as RFC 3629 restates it: no overlong forms, surrogates, code points above U+10FFFF, stray continuation bytes or sequences cut short. The compliance suite combines Markus Kuhn's UTF-8 stress test, WPT's fatal TextDecoder tests, every lead byte against the edges of its allowed ranges, errors at every offset around 16-, 32- and 64-byte blocks and at the end of every length up to 130 bytes, large inputs, and seeded random text. simdutf, Python and a Table 3-7 reference agree on every answer.
Run the full compliance suite locally. Replace your-component.wasm
with your compiled component.
Download the suite
curl -fLo validate_utf8.comply.wasm https://calculated.world/comply/validate_utf8.wasm
npx qipok your-component.wasm --suite validate_utf8.comply.wasm
764 of 7,246 cases · 764 true · 0 false
| Case | Name | Expected | Note | Size |
|---|---|---|---|---|
| 005813 | generated/0505 Generated | true | 15 B | |
| 005815 | generated/0507 Generated | true | 206 B | |
| 005819 | generated/0511 Generated | true | 54 B | |
| 005821 | generated/0513 Generated | true | 67 B | |
| 005830 | generated/0522 Generated | true | 33 B | |
| 005833 | generated/0525 Generated | true | 48 B | |
| 005834 | generated/0526 Generated | true | 106 B | |
| 005837 | generated/0531 Generated | true | 313 B | |
| 005838 | generated/0532 Generated | true | 68 B | |
| 005839 | generated/0534 Generated | true | 15 B | |
| 005840 | generated/0535 Generated | true | 379 B | |
| 005841 | generated/0536 Generated | true | 69 B | |
| 005842 | generated/0537 Generated | true | 76 B | |
| 005844 | generated/0539 Generated | true | 346 B | |
| 005846 | generated/0541 Generated | true | 263 B | |
| 005851 | generated/0546 Generated | true | 185 B | |
| 005854 | generated/0549 Generated | true | 335 B | |
| 005855 | generated/0550 Generated | true | 8 B | |
| 005858 | generated/0553 Generated | true | 52 B | |
| 005859 | generated/0554 Generated | true | 367 B | |
| 005862 | generated/0557 Generated | true | 91 B | |
| 005864 | generated/0560 Generated | true | 87 B | |
| 005868 | generated/0564 Generated | true | 293 B | |
| 005870 | generated/0566 Generated | true | 41 B | |
| 005873 | generated/0569 Generated | true | 14 B | |
| 005878 | generated/0574 Generated | true | 243 B | |
| 005884 | generated/0580 Generated | true | 186 B | |
| 005891 | generated/0587 Generated | true | 34 B | |
| 005897 | generated/0593 Generated | true | 376 B | |
| 005900 | generated/0596 Generated | true | 23 B | |
| 005901 | generated/0597 Generated | true | 5 B | |
| 005904 | generated/0600 Generated | true | 280 B | |
| 005905 | generated/0601 Generated | true | 8 B | |
| 005906 | generated/0602 Generated | true | 32 B | |
| 005907 | generated/0603 Generated | true | 28 B | |
| 005908 | generated/0604 Generated | true | 10 B | |
| 005909 | generated/0605 Generated | true | 398 B | |
| 005911 | generated/0607 Generated | true | 399 B | |
| 005912 | generated/0608 Generated | true | 80 B | |
| 005916 | generated/0613 Generated | true | 369 B | |
| 005918 | generated/0615 Generated | true | 55 B | |
| 005923 | generated/0620 Generated | true | 16 B | |
| 005928 | generated/0626 Generated | true | 59 B | |
| 005929 | generated/0627 Generated | true | 13 B | |
| 005930 | generated/0628 Generated | true | 359 B | |
| 005932 | generated/0630 Generated | true | 63 B | |
| 005933 | generated/0631 Generated | true | 10 B | |
| 005934 | generated/0632 Generated | true | 14 B | |
| 005935 | generated/0633 Generated | true | 46 B | |
| 005941 | generated/0639 Generated | true | 391 B |
Where these rules come from
Well-formed UTF-8 is defined by Table 3-7 of
the Unicode Standard, chapter 3
, which
RFC 3629
restates as ABNF. Every answer is agreed by
simdutf
9.4.0, Python’s strict codec and a direct reading of the table; the
suite’s own tests add Node.js’s buffer.isUtf8
and a fatal TextDecoder.
- UTF-8 decoder capability and stress test — Markus Kuhn’s file, the source of the 80 Kuhn cases
-
WPT textdecoder-fatal tests
— what browsers must reject when decoding with
fatal: true - Validating UTF-8 In Less Than One Instruction Per Byte — John Keiser and Daniel Lemire’s vectorised algorithm, which simdutf uses