Want to parse online TSV file and save to Clipper?
Try Withdata FileToDB, a desktop TSV to Clipper converter for Windows, MacOS, and Linux, Import cloud TSV to Clipper, Easy and Fast.
- Can run in GUI mode, Step by Step, just a few mouse clicks.
- Can run in Command line, for Scheduled Tasks and Streams.
- Convert locally and securely, avoid uploading large or private TSV file(s) to online services.
Download Withdata FileToDB
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
Import cloud TSV file to Clipper table
Choose Clipper and logon.
Click “Wizard – 1 File To 1 Table” at task dialog.
Select “Source Type” with “Url”.
then show the wizard.
1. Input the TSV file URL, and download the file.
2. Open the saved TSV file.
3. Config target Clipper table.
4. Set rows options.
5. Import cloud TSV to Clipper.
See Clipper table
Import cloud TSV to Clipper in command line
Save “TSV to Clipper” session, then you can:
- Import cloud TSV to Clipper in Windows command line.
- Import cloud TSV to Clipper in Linux command line.
- Import cloud TSV to Clipper in macOS command line.
Set scheduled tasks for importing cloud TSV to Clipper
You can schedule and automate this converting task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “TSV to Clipper” conversion.
- Set scheduled task for “TSV to Clipper” conversion.
FAQ
More about Withdata FileToDB – TSV to Clipper converter
Download Withdata FileToDB
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
TSV → Clipper reference
Type mapping
| Value kind | in TSV | in Clipper |
|---|---|---|
| Int | 1234 | Numeric(10,0) |
| Bigint | 9007199254740993 | Numeric(19,0) |
| Decimal | 1234.56 | Numeric(p,s) |
| Float | 1.234e+10 | Float |
| Text | unquoted; a tab in the value splits the column | Character(n) |
| Long text | unquoted; newlines break the row | Memo |
| Date | 2026-09-18 | Date |
| Datetime | 2026-09-18 14:30:00 | (none) |
| Binary | not representable | (none) |
| Boolean | TRUE / FALSE | Logical |
| JSON | the whole JSON value as-is (its own quotes stay) | (none) |
Dialect differences
TSV is a file format and Clipper is a database server, so the target has to be told the types the file never carried - the rows below are where the two sides diverge.
| Property | in TSV | in Clipper |
|---|---|---|
| port | — | (file-based) |
| identifiers | Rarely used, which is exactly why tabs in data break it | — |
| row limit | — | (driver dependent) |
| dates | Conventional text: 2026-09-18 or 2026-09-18 14:30:00 | Date (D) |
| long text | — | Memo (M) |
| binary | Not supported - must be encoded | — |
| separator | Tab | — |
| encoding | No declaration - UTF-8 works only with a BOM | — |
| typing | None - every field is text | — |
| shape | Flat table, optional header row | Tables of rows and columns |
| ceiling | No formal limit | — |
No counterpart
- TSV values of kind Date and time have nowhere to go in Clipper.
- TSV values of kind Binary have nowhere to go in Clipper.
- TSV values of kind JSON have nowhere to go in Clipper.
Convert your data online, free
Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.
New to the format? Read what a TSV file is (and how it differs from CSV).