uDocumentViewer
Data & Config.dbf

DBF viewer

ready
About DBF

dBase / Foxpro / Shapefile attribute table.

DBF is the dBase-era table format — a fixed-width binary header followed by fixed-width records — that quietly survives inside ESRI Shapefiles, FoxPro databases, Clipper applications, and a long tail of legacy line-of-business software. We parse the header directly in the browser (no dependency required), enumerate the field descriptors, and decode common types: Character, Numeric, Float, Logical, Date, Integer, and Memo references. A pick-list of legacy code pages (cp1252, cp437, cp850, iso-8859-1) lets you correct mis-rendered accented characters. Deleted records (marked with the '*' sentinel) are skipped; the toolbar shows the file's true record count.

FAQ
What is a DBF file?
DBF is dBase's table file format from the 1980s. It outlived dBase itself because ESRI Shapefiles store their attribute table as a sidecar .dbf, and because countless legacy systems still write it.
Why is my text full of question marks?
DBF files don't store their text encoding. We default to cp1252 (Windows Latin-1) which is correct for most western data. If your records look garbled, try cp437, cp850, or iso-8859-1 from the encoding dropdown.
What about Memo (M) fields?
Memo values live in a sidecar .dbt or .fpt file. Without that file we can only show the block reference; with the sidecar you'd need to merge them by hand for now.
Is my file uploaded?
No. The bytes are parsed locally in your browser; the file never leaves your device.
Does it work on mobile?
Yes. The records table scrolls horizontally with a sticky row index, and the schema view stacks comfortably on narrow viewports.
More Data & Config