Working in or with Japan means business cards — lots of them, in two writing systems. Most scanner round-ups are written for a Western audience and never test a single kanji card. This comparison does the opposite: every tool below is judged first on how it handles a Japanese meishi, then on price and everything else.
| App | Japanese cards | English UI | Free tier | Paid from | Best for |
|---|---|---|---|---|---|
| Eight | Excellent | Limited | Generous | Premium ~¥480/mo | Japanese-speaking individuals |
| Sansan | Excellent | Partial | None | Enterprise pricing (quote) | Large Japanese enterprises |
| CamCard | Partial | Yes | Small | ~$5/mo | Global travellers, English cards |
| HiHello | Weak | Yes | 5 scans/mo | ~$6/mo | Digital-card-first users |
| Covve | Weak | Yes | Limited | $12–31/seat | Relationship-CRM buyers |
| meishiscan | Excellent | Yes (5 languages) | 20 scans/mo | ¥780/$5.90/mo | Bilingual teams and professionals |
Any modern OCR can recognise kanji characters. The test that separates the tools is what happens next: does 山田太郎 land in a Japanese-name field with "Taro Yamada" beside it and the furigana preserved — or does one overwrite the other? Does 代表取締役 become "Representative Director", or stay untranslated in a field you can't search? Does the English back of the card merge into the same contact as the Japanese front?
Eight and Sansan pass these tests — they were built in Japan. The Western tools mostly don't. The catch runs the other way, too: Eight and Sansan assume a Japanese-reading user, so the English half of a bilingual contact base gets second-class treatment, and their interfaces are hard going for non-Japanese colleagues.
Related: using Eight or Sansan when you don't read Japanese · what a proper Japanese card scan looks like