Free online DB to DBF converter
Convert database tables from DB files to compatible standalone DBF files.
Convert DB to DBF online - free
Your file is processed automatically and deleted right after you download the result, or after 3 hours at the latest.
Import a file from a URL
Paste a direct link to the file. We download it to our server and it is converted exactly like an upload.
How it works
-
1/3
Upload your .db file
Click to browse to select your file you want to convert or simply drag & drop your file into selected area.
-
2/3
Perform .db to .dbf conversion
After successful file upload, click to convert when you are ready.
-
3/3
Download converted .dbf file
Conversion result is ready to download.
Conversion statistics: DB to DBF
Updated November 15, 2026, from conversions on 101convert.com
How to convert db to dbf file
- Databases
- No ratings yet.
A legacy GIS, accounting, or reporting program may require a standalone .dbf table while the data is stored in a .db database. Conversion exports selected records into the older dBase format, but it does not preserve the source database's full structure.
What the DB format is
.db is a generic database filename extension, not one universal format. In this context it may identify a SQLite database, a proprietary application database, Berkeley DB, or another database engine. The creating application or database signature must be identified before choosing a conversion method.
SQLite files commonly contain multiple tables, indexes, views, constraints, and triggers in one file. A SQLite-specific converter cannot read every file named .db. For a suspected SQLite file, run sqlite3 source.db ".tables"; a table listing confirms that the SQLite command-line tool can open it. Use sqlite3 source.db ".schema table_name" to inspect the table structure.
What the DBF format is
.dbf is the table format associated with dBase and FoxPro. It stores rows and columns in a standalone file and is supported by many older accounting, GIS, spreadsheet, and desktop database applications. A shapefile normally uses a DBF file for its attribute table.
DBF is suitable when the receiving application expects a simple table without a database server. A typical DBF file represents one table, not an entire relational database. Common legacy dialects restrict field names to 10 characters and provide basic character, numeric, date, and logical fields. Tables, relationships, indexes, views, triggers, constraints, permissions, and application logic from the source are not carried over.
How to convert DB to DBF
For a one-time conversion, use the converter on 101convert.com without installing software. Upload the .db file, select DBF when the source type is recognized and the required table can be selected, start the conversion, and download the result. A generic .db file may not be identifiable; in that case, open it with the application that created it and export the required table as CSV or use that application's DBF export.
For a SQLite database, a controlled script gives better control over table selection and data types. Install the Python package:
pip install dbf
The following example exports three columns from a customers table:
import sqlite3
import datetime
import dbf
source = sqlite3.connect("source.db")
rows = source.execute(
"SELECT id, name, created FROM customers"
).fetchall()
output = dbf.Table(
"customers.dbf",
"id N(10,0); name C(80); created D"
)
output.open(mode=dbf.READ_WRITE)
for customer_id, name, created in rows:
created_date = (
datetime.date.fromisoformat(created[:10])
if created else None
)
output.append((customer_id, name, created_date))
output.close()
source.close()
Change the SQL query and DBF definition to match the source. Use C(length) for text, N(width,decimals) for numbers, D for dates, and L for logical values. Convert timestamps, nulls, JSON, and other non-DBF values explicitly rather than allowing them to be guessed as text.
A graphical alternative is to export the selected table to CSV from the source application, then open the CSV in software that supports dBase output and choose File → Save As or File → Export with DBF or dBase selected. Confirm the delimiter, character encoding, date interpretation, decimal separator, and numeric columns before saving. CSV is only an intermediate table, so it does not preserve indexes, relationships, or database types reliably.
Quality and compatibility limits
Conversion is normally lossy. A source database with several tables requires a separate DBF file for each exported table. Foreign keys, joins, formulas, indexes, permissions, triggers, and application logic must be recreated separately.
BLOBs, long text, JSON, high-precision decimals, timezone-aware timestamps, and Unicode characters may be truncated, rounded, rejected, or converted to text. Older dBase programs may not support long field names, large character fields, memo fields, null values, or newer date-time variants. Use the DBF dialect and code page required by the destination program; UTF-8 support varies, and many older programs expect a legacy encoding such as Windows-1252.
After conversion, compare source and output row counts, inspect nulls, dates, decimal precision, accented characters, and maximum text lengths, then open the file in the actual destination application. Keep the original .db file because DBF cannot generally reproduce the complete source database.
DB vs DBF: format comparison
How the DB and DBF formats compare on the properties that matter most for this conversion.
| Property | .DB Database file | .DBF dBASE Database File |
|---|---|---|
| Plain-text readable | No | No |
| Data types | Typed | Typed |
| Nested structures | — | No |
| Formulas | No | No |
| Multiple tables or sheets | Yes | No |
| Typical file size | Medium | Small |
| Open standard | Partly open | Partly open |
| Best used for | Data exchange | Data exchange |
| Introduced | — | 1983 |
| Developer | — | Ashton-Tate / dBASE, Inc. (format origin) |
| MIME type | — | application/x-dbf |
Information about file extensions and file types is provided by File-Extensions.org
Suggested software and links: db to dbf converters
Frequently asked questions
Is the DB to DBF converter free?
Yes, converting DB to DBF on 101convert.com is completely free. No registration, email address or installation is required. If you need a higher file size limit or want to convert more files at once, see our plans.
How large can my DB file be?
You can upload DB files up to 10 MB and convert up to 3 files at once in a single batch. With a paid plan the limit is up to 50 MB per file and 20 files at once, see our plans.
What happens to my uploaded files?
Files are processed automatically. Your upload is deleted from our servers right after you download the result, or after 3 hours at the latest. We never view or share your files.
Do I need to install any software to convert DB to DBF?
No. The DB to DBF conversion runs entirely online in your browser and works on Windows, Mac, Linux, Android and iPhone.
Did the conversion fail?
In most cases, the cause is an incorrect file format. Please upload a valid DB file for this DB to DBF conversion. Occasionally, the issue may be on our side. We analyze recurring conversion failures and disable or fix the converter if we detect a defect.
Will converting a DB file to DBF keep all my tables and relationships?
No, DBF is a standalone table format, so relationships, queries, constraints, triggers, and other database-wide features are not preserved. A source database with multiple tables generally needs each table handled separately.
What data can be lost when converting DB to DBF?
DBF supports a more limited set of field types, so binary data, complex values, and some date or time representations may be changed, converted to text, or omitted. Long field names and values may also be shortened when required by the DBF variant.
Will my DB file still be editable after converting it to DBF?
The result remains editable as a DBF table, but it is no longer a complete copy of the original database. Database-level objects such as indexes, relationships, validation rules, and queries may need to be recreated.
Why are some DB fields blank or incorrectly formatted in the DBF result?
This usually happens when a source field uses a type that DBF does not support directly, such as binary or complex data, or when values exceed DBF field limits. The exact result depends on the structure and data types used by the source DB file.
Additional formats for
db file conversion
- db to txt
- db to csv
- db to mdb
- db to json
- db to pdf
- db to excel
- db to vcs
- db to accdb
- db to db3
- db to sqlite3
- db to abs
- db to ave
- db to bmp
- db to crypt5
- db to crypt6
- db to crypt7
- db to cs
- db to cvs
- db to db2
- db to dbs
- db to docx
- db to fdb
- db to gdb
- db to html
- db to ics
- db to inp
- db to mbk
- db to mdf
- db to mdn
- db to myd
- db to odt
- db to pd
- db to rtf
- db to s3db
- db to sdf
- db to sql
- db to sqlite
- db to text
- db to vcard
- db to xlr
- db to xls
- db to xlsm
- db to xlsx
- db to xml
Reverse conversion
Convert to dbf from
other formats
- fox to dbf
- fxp to dbf
- xls to dbf
- csv to dbf
- mdb to dbf
- sdf to dbf
- xlsx to dbf
- sqlite to dbf
- accdb to dbf
- fdb to dbf
- adb to dbf
- crp to dbf
- db2 to dbf
- dbc to dbf
- dbt to dbf
- dbv to dbf
- dbx to dbf
- doc to dbf
- fmp to dbf
- fpt to dbf
- frc to dbf
- fwp to dbf
- gdb to dbf
- jpg to dbf
- lbl to dbf
- ndx to dbf
- ntx to dbf
- odb to dbf
- ods to dbf
- otg to dbf
- pmw to dbf
- sda to dbf
- sdd to dbf
- smf to dbf
- spr to dbf
- stc to dbf
- str to dbf
- sxc to dbf
- sxi to dbf
- tbk to dbf
- txt to dbf
- uos to dbf
- uot to dbf
- vor to dbf
- wfm to dbf
- xlsb to dbf
- xlsm to dbf
- xltx to dbf