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
187 of 7,246 cases · 33 true · 154 false
| Case | Name | Expected | Note | Size |
|---|---|---|---|---|
| 006451 | generated/1170 Generated | false | 9 B | |
| 006455 | generated/1174 Generated | true | 32 B | |
| 006461 | generated/1180 Generated | false | 213 B | |
| 006467 | generated/1187 Generated | true | 265 B | |
| 006468 | generated/1188 Generated | true | 7 B | |
| 006479 | generated/1199 Generated | true | 19 B | |
| 006495 | generated/1215 Generated | false | 285 B | |
| 006504 | generated/1224 Generated | false | 41 B | |
| 006506 | generated/1226 Generated | false | 10 B | |
| 006515 | generated/1236 Generated | false | 307 B | |
| 006524 | generated/1245 Generated | true | 197 B | |
| 006529 | generated/1250 Generated | false | 150 B | |
| 006531 | generated/1252 Generated | true | 300 B | |
| 006542 | generated/1264 Generated | false | 17 B | |
| 006549 | generated/1271 Generated | false | 7 B | |
| 006552 | generated/1274 Generated | false | 162 B | |
| 006554 | generated/1276 Generated | false | 321 B | |
| 006560 | generated/1283 Generated | false | 7 B | |
| 006562 | generated/1285 Generated | false | 281 B | |
| 006578 | generated/1301 Generated | false | 63 B | |
| 006597 | generated/1321 Generated | false | 304 B | |
| 006610 | generated/1334 Generated | false | 49 B | |
| 006629 | generated/1353 Generated | false | 54 B | |
| 006633 | generated/1357 Generated | false | 389 B | |
| 006642 | generated/1366 Generated | false | 3 B | |
| 006647 | generated/1373 Generated | false | 12 B | |
| 006648 | generated/1375 Generated | true | 152 B | |
| 006660 | generated/1387 Generated | false | 37 B | |
| 006664 | generated/1391 Generated | false | 12 B | |
| 006667 | generated/1395 Generated | true | 11 B | |
| 006669 | generated/1397 Generated | true | 11 B | |
| 006682 | generated/1410 Generated | false | 360 B | |
| 006684 | generated/1412 Generated | false | 66 B | |
| 006693 | generated/1422 Generated | false | 378 B | |
| 006708 | generated/1437 Generated | false | 75 B | |
| 006714 | generated/1444 Generated | false | 5 B | |
| 006718 | generated/1449 Generated | false | 30 B | |
| 006734 | generated/1465 Generated | false | 5 B | |
| 006749 | generated/1481 Generated | false | 400 B | |
| 006754 | generated/1486 Generated | false | 7 B | |
| 006770 | generated/1502 Generated | false | 3 B | |
| 006784 | generated/1517 Generated | false | 5 B | |
| 006785 | generated/1518 Generated | false | 2 B | |
| 006789 | generated/1523 Generated | false | 17 B | |
| 006807 | generated/1543 Generated | false | 40 B | |
| 006812 | generated/1548 Generated | false | 5 B | |
| 006823 | generated/1560 Generated | true | 365 B | |
| 006857 | generated/1595 Generated | false | 235 B | |
| 006860 | generated/1598 Generated | false | 27 B | |
| 006861 | generated/1599 Generated | false | 360 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