BINARY DATA · READABLE EVIDENCE

Legacy DBF Table Reader

Inspect legacy dbf table reader with typed values, byte locations and portable decoded exports.

Original sources preservedReview before exportSave & reopen projects

Original sources stay unchanged · save your review to keep decisions

Reads supported dBASE/FoxPro fixed records, deletion flags, text, dates, logical, integer and double fields. ASCII numeric values stay decimal text. Memo pointers are retained without sidecar data. Encoding is explicitly selected; encrypted/extended types are unsupported.

Using Legacy DBF Table Reader

Inspect legacy dbf table reader with typed values, byte locations and portable decoded exports.

  1. Open supported files in their intended order, or try the ready worked example. Binary formats use exact local files; tabular formats use a header row or JSON objects.
  2. Open Details & settings to choose explicit fields, rules or methods. Select a record to inspect its source evidence and add review notes. Import-repair replacements require individual approval.
  3. Use Preview for result tables, metrics, charts and method assumptions. Review missingness, warnings and unsupported features before relying on a result.
  4. Download the workflow ZIP for data, task-specific artifacts, settings and source fingerprints. Save review to reopen your decisions with the exact original files.

Example

The ready binary file contains small labeled records with text, typed numbers or an exact integer above JavaScript’s safe range. Review byte offsets and the embedded/declared schema, then download the decoded-data package. Tags and exact integers remain explicit in JSON.

Questions & answers

What does Legacy DBF Table Reader support?

Reads supported dBASE/FoxPro fixed records, deletion flags, text, dates, logical, integer and double fields. ASCII numeric values stay decimal text. Memo pointers are retained without sidecar data. Encoding is explicitly selected; encrypted/extended types are unsupported.

What is in the downloads?

The primary ZIP includes result CSV/JSON, findings, source fingerprints, settings and task-specific artifacts described by the tool. Analysis workflows also include chart SVGs when applicable. CSV formula escaping is on by default; JSON preserves types and exact tagged binary values. Original sources can be downloaded separately.

Can I reopen my work and are files sent to a server?

Processing runs locally in this browser with local libraries and bounded workers. Save review retains settings, decisions and exact source fingerprints; reopen it with the matching original files. Sources are not automatically uploaded or fetched from URLs. Public pages retain the site’s approved ads and optional analytics.

What are the practical limits and review requirements?

Up to eight files and 80 MiB total, normally 25 MiB per file. The line slicer accepts an 80 MiB source and exports up to 25 MiB. Data workflows support 50,000 rows and 300 columns; binary parsers have depth/object guards and analysis simulations have explicit work budgets and a 30-second timeout. Review source evidence, assumptions and the result in your target application; unsupported features are not silently treated as supported.

KEEP YOUR WORKFLOW MOVING

A useful next step for your task.

Browse Developer & Data

Help improve this tool

Report a problem or suggest an improvement

Describe the issue without pasting private tool input. Feedback goes to our admin inbox.

Find another tool · Read practical guides