Takeout upload problems
The Local file (Google Takeout) path uploads your export through the browser to WordPress. Failures are usually file size, format, or server PHP limits.
Supported files
- .zip or .tgz from Google Takeout with Blogger selected
- Single .atom or .xml Blogger export (no zip required)
If Takeout split your export into multiple parts, upload all parts when prompted.
Upload size limits
PHP settings on your host cap uploads:
| Setting | Typical issue |
| upload_max_filesize | File rejected before processing |
| post_max_size | Must be ≥ upload size |
| Web server body limit | nginx client_max_body_size |
Fix: Ask your host to raise limits for your admin URL, or upload a smaller export:
- Export one Blogger site only (not entire Google account)
- Use .tgz if offered
- Split very large blogs into smaller Takeout jobs
Corrupt or invalid archive
- Re-download from Google Takeout — do not open/re-zip on Mac (avoids __MACOSX junk)
- Upload the original .zip in WordPress; do not unzip first
- Try a single .atom export for a quick test
ZIP extension missing
The plugin needs PHP ZIP support for .zip archives. Check MigraSync → General → System Requirements. If ZIP is missing, ask your host to enable zip extension, or upload .tgz / .atom instead.
Upload succeeds but parse fails
- Wrong file type (not Blogger export)
- Incomplete download — verify file size matches Google’s report
- Encrypted or password-protected zip — Takeout exports are not password-protected by default
Related
Related Articles
On this page