Check CSV
Files are processed in your browser and are not sent to our server.
Result
| Severity | Row | Column | Issue | Value |
|---|
FREE WEB TOOL
Check CSV syntax, encoding, tab-delimited conversion, and the standard 1,000-row limit before e-Hiden III import.
Files are processed in your browser and are not sent to our server.
| Severity | Row | Column | Issue | Value |
|---|
e-Hiden III can import CSV, Excel, and fixed-length files. For CSV, however, looking like a table is not enough. Excel can turn a CSV into tab-delimited text, and broken quoting can also stop an import.
This checker focuses on those file-format problems before upload. If encoding is unclear, use the CSV encoding & delimiter inspector next.
This is easy to confuse with e-Hiden III Evo. Standard e-Hiden III accepts a file of up to 1,000 rows including the header. The 5,000-record workflow belongs to the separate Evo tool.
This checker therefore reports more than 1,000 non-empty rows as an error for standard e-Hiden III. If your operation uses Evo, confirm the Evo-specific workflow instead.
Sagawa documents that e-Hiden III exports CSV as UTF-8 by default. In some older Excel workflows, saving that CSV can turn it into tab-delimited text and make re-import fail.
The checker flags files that repeatedly look like one-column rows containing TAB characters. The Excel-damaged CSV checker can help inspect other Excel-side changes.
CSV files carried over from e-Hiden II or e-Hiden Pro may use different field mappings or code values. Passing this checker does not mean those service-specific values are correct.
Compare the import mapping and current template inside e-Hiden III. To compare column names and order, use the CSV header diff checker.
Fix CSV syntax, tab-delimited conversion, and the 1,000-row limit first. If encoding is uncertain, verify how the source file was saved next.
The goal is not to promise a successful e-Hiden III import. It is to remove file-side causes that can be corrected before opening the import screen.