Import Failed or Times Out
2 min read1 viewUpdated on September 3, 2026
What to check when a kit import stalls or fails partway through.
Where the failure happens tells you the most about the cause: an import that fails right away almost always points to the file or a missing plugin, while one that starts fine and stalls partway through almost always points to a server limit.
Import fails immediately
Check that you downloaded a genuine
.zipfile from your ThemeForest Downloads tab (Main Files), not a folder or a single.json— some browsers auto-extract zip downloads, which breaks the import. Re-download if you're not sure.If the download was interrupted or your connection dropped partway through, the
.zipcan be silently corrupted — try opening it on your own computer first; if it won't open cleanly there either, download it again from ThemeForest.Make sure all required plugins (Template Kit – Import, Elementor, Jeg Elementor Kit, ElementsKit Lite, Gum Elementor Kit, MetForm) are active before importing — an inactive plugin is one of the most common causes of an immediate failure.
Confirm your host has the PHP Zip extension enabled — WordPress Admin → Tools → Site Health → Info → Server shows this. If it's missing, the import can't even open the file, and you'll need to ask your host to enable it.
Import starts, then stalls or times out partway through
Increase
max_execution_timeon your hosting if the import stalls partway through rather than failing immediately — that pattern specifically points to a timeout, not a missing plugin or a bad file.Try Single Import for one page at a time instead of the full bundle (see Import the Template Kit) — this both narrows down which specific page is causing trouble, and reduces the load on any single request.
If the failure happens right as the import seems to be finishing rather than partway through, it may be a gateway timeout on your host's side (sometimes shown as a "502" or "504" error) rather than a WordPress setting — this one needs to go to your hosting provider directly, since it happens outside WordPress's own limits.