Uploads multiply into thumbnails
One media upload can create many generated image sizes, so the number of files can grow much faster than the visible Media Library count.
← All tools
Free WordPress Tool
WordPress Inode & File Count Estimator
Estimate WordPress file-count pressure before moving to hosting plans that enforce inode or file limits.
Free to useNo account requiredRuns in your browser
Planning result
Ready
Adjust the inputs to generate a planning recommendation.
Technical explanation
How to interpret this tool before a WordPress migration
Inode limits are easy to miss because they are not the same as disk-space limits. A WordPress site can use modest storage while containing hundreds of thousands of small files from uploads, image sizes, caches, backups, staging copies and plugin directories.
Backups can distort counts
Extracted backups, staging directories and migration plugins may temporarily duplicate much of the WordPress tree.
Provider definitions vary
Some hosts count files, directories, mailboxes and cache files differently. Confirm the actual inode policy for the destination plan.
Practical questions
Is an inode the same as a file?
Practically for hosting limits, each file or directory often consumes an inode, though implementation details vary.
Why does migration need extra headroom?
Temporary archives and extracted copies may exist alongside production files during the move.
Can cache files cause inode problems?
Yes. File-based caches can create very large numbers of small files if not purged or controlled.