Measured export size · reader-verified destination limit
Check a WordPress database export against an import cap
Compare a measured WordPress database dump plus a chosen safety margin with an upload or import cap you verified for the destination method.
Check whether a measured WordPress database export plus your chosen safety margin fits a destination import limit that you verified. The worksheet does not inspect a file, host, or server.
Enter the measured export size, a margin from 0% upward, and the relevant destination limit.
How to choose the inputs
- Measure the actual database export file you plan to import. If you have not exported it yet, use a measured backup/export from the same site and export method as a planning reference.
- Check the documentation or account settings for the exact destination import route. Enter the smallest applicable file or request limit that the route documents; ask the host if the limit is unclear.
- Choose a margin to allow for a larger future export or differences in what the destination counts. The margin is your planning choice, not a standard or a promise that the import will work.
Method and limits
Required size scenario = measured dump size × (1 + margin ÷ 100). The worksheet compares that result with the destination cap and reports arithmetic headroom or shortfall. It uses decimal MB throughout and does not estimate compression, decompression, request overhead, database conversion, execution time, or server memory.
An upload cap is only one possible constraint. A provider, control panel, plugin, or command-line import path can have different limits and requirements. Verify the method you will actually use in the destination host's current documentation. A result that fits the entered cap does not establish that an import is supported or will complete.
WordPress migration guidance treats the database and site files as parts of a move. Keep a separate copy of the export and plan a tested restore path before changing a live site. This local worksheet does not receive or store the database file.
Related migration planning
Estimate file and database copy time with the migration transfer-time estimator, plan labor with the migration labor estimator, and review the site migration checklist.
Sources checked November 3, 2026
- WordPress Developer Resources: Migrating WordPress — migration guidance covering the site's files and database. Confirm the destination-specific import steps with your selected host.
- PHP manual: Core php.ini directives — documents PHP upload and POST size settings; these are examples of server-side limits and do not establish a particular host's database-import cap.
How it works
Enter the measured database export size, a safety margin you choose, and the applicable destination import or upload cap from the host or import method documentation. The worksheet calculates the required size scenario and arithmetic headroom or shortfall; it does not inspect your file or server.
Good to know
Does a result that fits mean the import will succeed?
No. It only compares the entered size scenario with the entered cap. The destination method may have other limits, configuration requirements, execution constraints, or compatibility issues. Verify the exact import path with your host and test an appropriate restore.
What safety margin should I use?
There is no universal margin. Choose one for your planning scenario based on your own measurements and how much the export may change. The worksheet does not assume compression or predict future database growth.
Does this upload or store my database?
No. The tool accepts size figures only and runs the arithmetic in your browser. Do not enter database contents or credentials.
Impact — TODO: apply/approval and configure referral URL — referral link not configured.
CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.
PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.