How to open DBF files without installing software and fix garbled text

DBF is not plain CSV: it includes field definitions

DBF is a tabular format with field names, types, lengths, and records rather than a plain delimited text file. DBF Viewer lets you inspect file information and field definitions before reviewing the rows.

Even if you eventually need CSV, checking the original DBF structure first makes text, numeric, date, and memo fields easier to understand.

• Review field names, types, and lengths
• Check the record count
• Inspect the original structure as well as values

Check the encoding when Japanese text is garbled

Older Japanese DBF files can show mojibake when the stored text is decoded with the wrong encoding. That does not necessarily mean the file is damaged.

Use Language Driver information as a clue, try Shift_JIS or Windows-31J, and verify several values such as names, addresses, company names, and notes instead of judging from a single cell.

• Try Shift_JIS
• Compare Windows-31J as well
• Verify multiple Japanese cells

DBT and FPT files can hold memo-field data

A matching .dbt or .fpt next to a DBF may contain long memo-field content such as notes or descriptions. Copying only the DBF can leave that data unavailable.

DBF Viewer can load the matching DBT/FPT and inspect memo content with the Cell Inspector. Use the original sidecar file rather than renaming one format to another.

• Keep matching DBT/FPT files with the DBF
• Inspect memo cells with Cell Inspector
• Preserve related files as a set

Deleted records may still remain in the DBF

Some DBF workflows mark rows as deleted while leaving the records in the file. DBF Viewer can show or hide those records when you are investigating backups or migration data.

The viewer is read-only: it does not undelete records or write changes back to the DBF.

Inspect large DBF files page by page

DBF Viewer displays records in pages. When a file has many fields, narrow the visible columns and sort the current page to focus on IDs, dates, names, or other relevant values.

Use Cell Inspector for long values such as addresses or memo content that do not fit comfortably in the table.

CSV export covers the currently displayed page

When you need data in a spreadsheet, the currently displayed page can be copied or saved as UTF-8 CSV after you have confirmed the encoding.

DBF Viewer is not a whole-file batch converter. Converting hundreds of thousands of rows or automating many DBF conversions requires a different workflow.

• Save the current page as UTF-8 CSV
• This is not whole-file batch conversion
• Review original field types before exporting

DBF has multiple dialects and field types

Files ending in .dbf do not all use exactly the same internal dialect. Multiple implementations and field types have existed over time, so DBF Viewer handles unknown field types conservatively rather than guessing.

Index files such as NDX, MDX, and CDX are not used. The viewer does not reproduce an original application's indexes or query behavior.

Investigate a copy without modifying the original

Although DBF Viewer itself is read-only, keep an untouched copy of legacy business data and inspect a working copy when possible. Preserve matching DBT/FPT files together with the DBF.

Selected DBF and DBT/FPT files are read in the browser rather than uploaded to a Browser Kitty backend for analysis. A saved single-HTML copy can also be opened locally.

Tips and limitations

• Mojibake and file corruption are different problems. If changing encodings does not make the structure readable, the file may be damaged or use an unsupported dialect.
• Keep DBT/FPT sidecar files with their DBF instead of copying only the DBF.
• Before exporting CSV, review DBF field types and memo usage so you understand what may be lost in a flat text export.
• NDX, MDX, and CDX indexes are not used; this viewer does not recreate an original application's indexing behavior.
• Preserve the original legacy data and perform investigation on a working copy.