Blogger XML to WordPress Converter

Convert a Blogger XML backup into a WordPress-compatible WXR file. Review the content you want to move, configure how labels and images are handled, then import the generated file into WordPress with the WordPress Importer.

If you are moving an entire Blogger site, this page also explains what the XML conversion does, what it does not migrate, and what you should check after the import.

Published by Blogger to WordPress · Last updated 24 September 2026

Convert Blogger XML to WordPress in 5 steps

Moving content from Blogger to WordPress starts with a Blogger XML backup. The converter turns that backup into a WordPress eXtended RSS (WXR) file that can be imported through WordPress.

  1. 1. Export your Blogger XML backup

    In Blogger, go to Settings → Manage blog → Back up content. Blogger sends you to Google Takeout, which delivers a ZIP file by email link or to Google Drive. You can upload that ZIP directly, or the feed.atom file inside it, or an older Blogger .xml backup. The backup can contain posts, pages, labels and comments. Keep the original file until you have checked the WordPress import and confirmed your content is complete. You can also sign in with Google and pick a blog directly instead of uploading a file.

  2. 2. Upload the XML file

    Come back to this converter and upload your Blogger XML backup. Large files are uploaded in chunks, subject to the limits shown by the converter. After the upload is complete, the file is scanned so you can review the available content before generating the WordPress file.

  3. 3. Review the content to migrate

    Before the WordPress file is created, review what was found in your backup. Depending on the backup, you can filter by content type, label, date and publication status, then choose exactly which posts and pages to bring over. This lets you leave out old, duplicate, test or unwanted content.

  4. 4. Configure categories, images, and other options

    Choose how Blogger labels are handled (import all as categories, skip them, or map only selected ones), decide whether to keep or rewrite image URLs, pick the permalink structure to target, and decide whether to include comments and draft posts. These options affect how your imported content is organized, so review them before generating the file.

  5. 5. Download the WXR file and import it into WordPress

    When the conversion is complete, download the generated WordPress XML file. In your WordPress dashboard open Tools → Import, install the WordPress Importer if prompted, upload the file and follow the prompts. After the import, review your posts, pages, categories, authors, comments, images and links before considering the migration complete.

Upload your Blogger XML

What does the Blogger XML converter move?

A Blogger XML backup can contain several types of content. The exact result depends on what is present in your backup and which options you select.

Posts

Published Blogger posts are converted into WordPress posts in the generated WXR file. After importing, check formatting, publication dates, authors, categories and links.

Pages

Blogger pages can be included and imported as WordPress pages. Review the page hierarchy and navigation after the import, because your WordPress theme and menus are configured separately.

Labels and categories

Blogger organizes content with labels; WordPress uses categories and tags. The converter can turn labels into WordPress categories according to the option you choose. For a large site, clean up outdated or duplicate labels first.

Comments

If comments are present in the source backup and you choose to include them, they are written into the generated WordPress XML. Review imported comments afterward, because comment settings and moderation are controlled by WordPress.

Drafts

Draft posts can be included when you enable that option. If your blog contains unfinished posts you do not want on the new site, check your selection before generating the WXR file.

Images and media references

You can keep the existing Blogger/Googleusercontent image URLs or rewrite them to a WordPress uploads path if you plan to move the images yourself. The right choice depends on your migration plan; see the image section below.

What the converter does not migrate automatically

Converting an XML backup is an important part of a Blogger-to-WordPress migration, but it is not the same as rebuilding the whole website. An XML conversion does not automatically recreate:

  • Blogger themes and theme customizations
  • Blogger widgets and layout settings
  • WordPress plugins and their settings
  • WordPress theme configuration
  • Navigation menus that depend on your WordPress theme
  • External services and integrations
  • SEO settings from third-party Blogger tools
  • Redirect rules on your server. The converter can generate a best-effort 301 redirect map, but you still need to apply it and test it.

After importing the content, configure the WordPress site separately and test the migration.

Before you migrate from Blogger to WordPress

Prepare these items before you start:

  • A current Blogger XML backup.
  • Access to the WordPress website where the content will be imported.
  • A recent backup of the WordPress site.
  • The WordPress Importer plugin.
  • A plan for handling images.
  • A plan for preserving or redirecting important Blogger URLs.
  • Enough time to review the imported content before changing DNS or retiring the old site.

For a large or important website, run a test import before completing the final migration.

How to import the WXR file into WordPress

After you download the converted WXR file:

  1. Log in to your WordPress dashboard.
  2. Open Tools → Import.
  3. Install and activate the WordPress Importer if it is not already installed.
  4. If the converter also produced an images ZIP, upload its contents to wp-content/uploads/b2w-import/ on your WordPress site before running the import.
  5. Choose the generated WXR/XML file.
  6. Follow the importer prompts and map authors if WordPress asks you to.
  7. Start the import and wait for it to finish.
  8. Check the imported posts and pages.
  9. Verify categories, comments, images and internal links.

Do not delete your Blogger backup right away. Keep the original until you have verified the new WordPress site.

Images during a Blogger-to-WordPress migration

Images are one of the areas that deserve the most attention during a migration. You generally have two approaches, and neither is universally better.

Option 1: Keep the existing image URLs

Imported posts keep pointing to the original Blogger or Googleusercontent image URLs. This is simpler and needs no extra copying during the first migration, but your WordPress site stays dependent on those external image URLs.

Option 2: Move images to WordPress

Image references are rewritten to a WordPress uploads path, and you place the image files there yourself. This gives your site direct ownership of its media, but it takes additional storage and more verification.

Whichever approach you choose, inspect a few representative posts after import and confirm that images load correctly on desktop and mobile.

After import: WordPress migration checklist

Before declaring the migration complete, check the following.

Content

  • Posts and pages are present.
  • Publication dates are correct.
  • Authors are mapped correctly.
  • Categories are organized as expected.
  • Comments were imported when required.
  • Drafts were handled intentionally.

Media

  • Images load correctly.
  • Important images are stored where you expect them to be.
  • Broken image URLs have been identified.
  • Image filenames and alt text are reviewed where necessary.

Links and SEO

  • Internal links work.
  • Important old Blogger URLs have a redirect plan.
  • The WordPress canonical URL is correct.
  • The site is not accidentally set to noindex.
  • The XML sitemap is available.
  • Google Search Console is set up for the WordPress site.
  • Important URLs are inspected after the migration.

User experience

  • The site works on mobile devices.
  • Navigation menus and search work.
  • Forms work.
  • Important plugins and integrations work.
  • There are no obvious broken pages or missing media.

Blogger XML to WordPress: frequently asked questions

What file do I need from Blogger?

You need a Blogger backup. In Blogger, use Settings → Manage blog → Back up content, which delivers a ZIP through Google Takeout. Upload the ZIP (or the feed.atom file inside it) here; older Blogger .xml backups also work. Alternatively, you can sign in with Google and let this tool read your blog directly through the Blogger API.

Can I convert Blogger XML to a WordPress WXR file?

Yes. The converter turns a Blogger XML backup into a WordPress-compatible WXR file that follows the same WordPress eXtended RSS format WordPress itself produces, so it imports through Tools → Import.

Do I need WordPress Importer?

Yes. The generated WXR file is meant to be imported through the WordPress Importer. In WordPress, open Tools → Import and install the importer if it is not already available.

Will my Blogger posts become WordPress posts?

Yes. Blogger posts included in the conversion are represented as WordPress posts in the generated WXR file. Always review the imported content after the migration.

Will Blogger pages be converted to WordPress pages?

Blogger pages included in the source backup can be converted for import as WordPress pages. Review the final page structure and navigation after importing.

What happens to Blogger labels?

Blogger labels can be converted into WordPress categories. You can import all labels, skip them, or map only the ones you select. Review the category structure before importing a large site.

Can I migrate comments?

Comments in the Blogger backup can be included when the comments option is enabled. Check the imported comments and your WordPress discussion settings afterward.

What happens to images?

It depends on the option you select. You can keep the existing Blogger/Googleusercontent image URLs, or rewrite them to a WordPress uploads path when you plan to move the images yourself. Always test image loading after import.

Does this migrate my entire Blogger website?

No. XML conversion focuses on the content in the Blogger backup and the export options you select. It does not automatically recreate every Blogger theme setting, widget, plugin, WordPress configuration, integration or redirect rule.

Is the converted file stored permanently?

No. Uploaded Blogger XML files and generated WordPress XML files are deleted automatically after 72 hours, whether or not you created an account. Download the converted file and keep your own copy before the retention period ends.

Can I migrate a large Blogger blog?

Large backups can be uploaded in chunks, subject to the limits shown by the converter. For a large or business-critical site, test the conversion and import with a copy before the final migration.

Should I keep my Blogger site online after importing into WordPress?

Do not remove the old site until you have verified the new WordPress site and put a URL redirect plan in place. Keeping the original backup is also recommended.

Need a complete Blogger-to-WordPress migration?

If you are moving an entire blog rather than doing a one-off XML conversion, the full guide covers preparing the WordPress site, importing the WXR file, URL and redirect planning, SEO checks and final testing.

Read the Blogger to WordPress migration guide →

Ready to convert your Blogger backup?

Upload your Blogger XML file and generate a WordPress-compatible WXR file.

Upload your Blogger XML

Review your content and export settings before downloading the converted file. Keep a copy of your original Blogger backup until the WordPress migration has been verified.

Privacy and file retention

A Blogger XML backup can contain the content of your site and other information included in the export. Uploaded Blogger XML files and generated WordPress XML files are deleted automatically after 72 hours, and you can delete your data at any time. See the privacy policy for details on what the service processes. Read the privacy policy.