Skip to converter

DBF to XLSX — attributes a spreadsheet has no equivalent for

A mapping tool asks for Excel and the attribute table behind the layer is dBASE. The transfer moves field names and values into cells, and leaves the schema behind: a workbook has no place to record that a field was declared numeric, fixed-width, or indexed.

Cell formatting, colours, column widths and merged ranges are dropped; only stored values survive.

Drop files here or DBF, up to 12 MB
    Add a file to start.

    Processed on your device. Files aren’t sent anywhere.

    No sign-up. Nothing to install.

    Attributes a spreadsheet has no equivalent for

    The definition block describes storage. A grid describes positions. The two do not overlap.

    dBASE attributeOutcomeIn the workbook
    Field namecrossesheader cell
    Record valuechangedcell text
    Declared typedroppedno type declaration exists
    Declared widthdroppedno fixed-width cells
    Index metadatadroppedno index in a sheet
    Deleted recordsdroppednot exported

    Field types become cell values

    A date-typed field arrives as the characters stored in the record, not as a spreadsheet date. A numeric field arrives as text. The type information lived in the header, and the header is not part of the transfer.

    Read as bytes, not as text

    The file is binary, so the reader parses the structure rather than decoding the whole file as characters.

    Field names belong to the source schema, even when they look abbreviated or inconvenient in a worksheet. Keep a field-name mapping with the exported workbook if a later process expects the old names. Renaming a column for readability can break that handoff. Before changing anything, identify a few source records and confirm their values under the corresponding worksheet columns.

    • Records are fixed-length and read by field position.
    • Character fields keep the padding their declared width imposed.
    • Legacy files were written under a single-byte codepage, so accented values can arrive changed.
    • Values are written as UTF-8 text in the workbook.

    Questions

    Does the field type survive?
    No. The type declaration lives in the definition block, and a workbook has no equivalent, so values arrive as text.
    Why is a date not a spreadsheet date?
    The stored characters are copied into a cell. Nothing is reinterpreted as a calendar value.
    Will the join key still work?
    The key value is copied, so the join usually still works — but check that padding and accents did not change it.
    How many sheets does the workbook get?
    A DBF supplies one record table. This conversion does not combine related database tables or companion geographic files. For this browser route the source may be at most 12 MiB, and records beyond the first 20,000 output rows are not included.

    One sheet named after the file

    Sheet mode decides how many sheets the workbook has: First sheet writes one, All sheets writes every book found in the file. Sheet names are cleaned of characters a spreadsheet cannot use and shortened to the format's limit. The downloaded workbook keeps the source file's name.

    Checking the transferred table

    The attribute table is usually joined to geometry by a key, so a lost column breaks the join.

    1. Convert the .dbf file and download the workbook.
    2. Compare the header cells with the fields in the definition block.
    3. Trim padding left by fixed-width character fields.
    4. Confirm the join key column is present and unchanged.
    5. Convert numeric columns to numbers before calculating.

    Share this converter

    More sharing options