How to Import Blogger Images Into the WordPress Media Library

You migrated your Blogger posts to WordPress. The text looks fine. But open a few posts and check the image URLs — they still point at blogspot.com, blogger.googleusercontent.com, or bp.blogspot.com.

That is hotlinking. Your images live on Google’s servers, not in your WordPress Media Library. It works until it does not: slow page loads, broken images after leaving Blogger, weak SEO signals, and zero control if Google changes access rules.

The fix is straightforward in principle: download every image, upload it to WordPress, and rewrite post content to use local URLs. In practice, a blog with hundreds of posts and thousands of images makes that painful by hand.

This guide explains why Blogger images stay remote after a typical import, how to import them into the WordPress Media Library properly, and how MigraSync automates the two-phase pipeline during migration.

• Time estimate: Automated migration — images import during the same job as posts (minutes to hours by volume). Manual methods — hours to days for large blogs.
• What you will need:
  • A WordPress site (destination for migration)
  • Your Blogger content — via live API connection or Google Takeout export
  • MigraSync plugin for the automated path
  • Enough hosting disk space for your full image library

Why Blogger Images Do Not Land in WordPress Automatically

The default WordPress Importer (and many basic migration tools) import post HTML content as-is. Blogger embeds images as <img> tags pointing at Google CDN URLs. The importer copies that HTML into your core database tables — but it does not download the image files, create media attachment posts in WordPress, store files under your local directory, or rewrite source attributes to your domain.

The result is frustrating: posts exist in WordPress, but images are still rented from Google.

Common Blogger image URL patterns

Host / pattern	What it is
https://blogger.googleusercontent.com/img/...	Modern Blogger CDN (most common)
1.bp.blogspot.com to 4.bp.blogspot.com	Legacy Blogspot image hosts
lh3.googleusercontent.com (and lh4–lh6)	Older Google image URLs

Blogger often serves a smaller size in post HTML (s320, s400) even when a higher-resolution version exists. A proper import should fetch the full resolution when possible — not just whatever thumbnail appeared in the export.

Why Local Images Matter (SEO, Speed, Ownership)

Hotlinked (remote)	Local (Media Library)
Extra DNS + TLS requests to Google on every page view	Served directly from your host or CDN
Broken if Blogger assets move or restrict hotlinking	You maintain absolute control over the files
Image SEO credit goes to googleusercontent.com	Images inherit equity on your custom domain
Hard to optimize (WebP, lazy load, CDN rules)	Standard WordPress + plugin optimization
Backup plugins may miss remote assets completely	Automatically included in site backups

Google Image Search and page experience signals favor sites that serve their own media reliably. For a serious migration, local images are not optional.

Overview: The Two-Phase Image Pipeline

Professional Blogger migrations split work into two distinct phases:

1.Content Import:Phase 1.

Bring over all text posts, standalone pages, and reader comments. Labels are systematically transformed into standard WordPress categories, and authors are mapped to their new user accounts.

2.Media Ingest:Phase 2.

Scan the newly imported content block to parse out remote Blogger image URLs. Full-resolution files are downloaded directly into your media library directory, and all hardcoded layout sources are automatically rewritten to use local URLs.

MigraSync runs Phase 2 automatically after content import completes. Progress shows clearly within the migration wizard interface. You can safely close the browser tab — the ingestion engine continues to process your media files quietly in the background.

Method 1: Automated Import With MigraSync (Recommended)

If you are migrating with MigraSync, image import is built directly into the Blogger Migration wizard — no separate plugin or secondary steps required.

Prerequisites

1. Install and activate the MigraSync plugin.
2. Connect your API key under your Status dashboard.
3. Choose your preferred import method:
   • Google Blogger API: Sign in securely and select your target blog.
   • Google Takeout: Upload your archive file. If images are already inside the archive, MigraSync maps them locally without re-downloading from the CDN.

Step 1: Enable image import options (Wizard Step 3)

In your Import options, enable these recommended settings:

Option	What it does
Full-Res Image Backup	Downloads high-resolution Blogger/Google-hosted images into the Media Library; rewrites post references to local URLs.
Smart Image SEO	Adds alt text when missing (derived cleanly from the filename) and strips Blogger-specific markup bloat.
Auto-Featured Images	Sets the first in-post image automatically as the WordPress featured image.
Download External Images	Optional — attempts to sideload non-Blogger URLs (enable if posts embed third-party images you want local).

Step 2: Run migration

1. Accept the data processing consent.
2. Click Start migration.
3. Watch the progress bar advance: content import processes first, followed immediately by the media ingest phase.
4. On completion, check the summary screen — your Images imported count should match your expected volume.

Step 3: Verify images are local

1. Open Media → Library — new uploads should appear organized neatly by date.
2. Open a migrated post on the front end, right-click an image, and select Open image in new tab.
3. The URL structure should be https://yoursite.com/wp-content/uploads/... — not blogspot.com or googleusercontent.com.

Domains MigraSync downloads from

The pipeline recognizes Blogger-owned hosts, including:

• blogger.googleusercontent.com
• bp.blogspot.com (1–4)
• lh3–lh6.googleusercontent.com
• [www.blogger.com](https://www.blogger.com)

If a specific image cannot be downloaded, the original URL is safely kept in the post content and logged in the error summary — allowing the migration to continue without stopping the whole job.

Google Takeout path

When you upload a Takeout archive, images are often already inside the ZIP file under the blog folder. MigraSync detects, imports, and maps them locally without pulling from Google’s CDN again — which speeds up the process significantly for large media libraries.

Method 2: WordPress Importer + Manual Download (DIY)

Some bloggers attempt the built-in free path first.

Steps

1. Export Blogger: Navigate to Settings → Manage blog → Back up content and download the XML file.
2. WordPress: Go to Tools → Import → Blogger and run the importer.
3. Upload the XML file, map your authors, and process the import.

The Breakdown

This imports text posts with remote image URLs completely intact. You still need a secondary tool to localize your media assets — the default importer does not process files.

Tool / approach	Core Limitation
“Import external images” plugins	Frequently timeout on large blogs; often grab small thumbnails instead of full size.
Manual download per post	Completely unscalable if your blog has passed 20 posts.
Search-and-replace utilities	Changes links textually without creating actual Media Library attachments.
wget / curl command scripts	Requires terminal access; fails to generate attachment metadata; breaks on unique URL variants.

Method 3: Third-Party Migration Plugins

Plugins like All-in-One WP Migration, FG Blogger to WordPress, or custom standalone scripts vary wildly in production quality.

When evaluating alternative third-party tools, ensure they can answer these baseline performance questions:

• Does it create proper Media Library attachments or simply run textual hotlink replacements inside the post content?
• Does it actively fetch the full-resolution version or does it settle for the lower-res thumbnail variants?
• Does it seamlessly handle modern googleusercontent.com URL variations alongside legacy Blogspot paths?
• Does it feature robust timeout management on shared hosting when processing 500+ images?

MigraSync’s distinct operational advantage is its dedicated media ingest phase run sequentially after content parsing. It uses background processing with granular progress tracking specifically built for environments where a single web request cannot download everything at once.

When Manual / DIY Image Import Breaks

• Images show in editor but 404 on front end: The URL was rewritten incorrectly during a text replacement, but the physical file was never uploaded to your host.
• Only low-resolution images display: Your import tool grabbed the smaller preview URLs instead of the full-resolution target file.
• Import stops at 10–20 posts: You ran into a PHP timeout or memory limit restriction on a shared hosting environment.
• Media Library is empty but posts have images: Your site is relying entirely on hotlinks — no local attachments were created during the process.
• Duplicate images in the Media Library: Multiple structural imports were executed without proper data deduplication logic in place.
• %20 appears in filenames: Blogger encodes spaces directly into paths. If your migration tool does not normalize these into clean hyphens, your image SEO signals suffer.

Fixing Images After an Already-Completed Migration

If you already completed your migration in the past without localizing your images, you have three primary recovery options:

• Option A: Re-run migration on a staging site: Wipe a test site copy using a database purging tool or spin up a fresh WordPress install, then run MigraSync with Full-Res Image Backup enabled from the start.
• Option B: Media-only repair plugins: There are specific plugins that scan existing post_content for remote source links and attempt to sideload them into your attachments. Always test this on a staging backup first, as large blogs may require you to increase your hosting PHP memory limits.
• Option C: Selective manual fix: If you only have a few critical posts showing remote assets, download those images to your machine, upload them into the Media Library, and swap out the HTML sources manually. This is only viable for small, targeted fixes.

Image Import Checklist (Post-Migration)

• [ ] Media Library asset count roughly matches your expected historical image volume.
• [ ] A random sample of 10 posts confirms all images load directly from your uploads directory.
• [ ] Featured images are correctly assigned across key archive grids.
• [ ] Alternative text attributes are present on images to protect your accessibility scores.
• [ ] Page speed tests show zero request dependencies on old third-party image hosts.
• [ ] Google Search Console displays zero new image crawl errors.
• [ ] Your primary site backup strategy fully encompasses the newly populated uploads folder.

Large Blogs: What to Expect

Blog size	Typical image behavior
Under 100 posts	Often completes entirely within a single, brief browser session.
500–2,000 posts	The media phase may run for 30+ minutes; background processing handles this safely.
2,000+ posts	We highly recommend utilizing the Takeout archive path to avoid running into API quota freezes.
Image-heavy sites	Ensure your web hosting disk quota is adequate and double-check completion summary counts.

Smart Image SEO & Auto-Featured Images

Blogger image HTML often includes heavy layout wrappers, duplicate resize parameters, and empty link targets. Enabling Smart Image SEO handles cleaning this up programmatically:

• It automatically builds humanized alt text tags out of filenames when missing.
• It strips away legacy, platform-specific code bloat from your image tags.
• It perfectly preserves any custom alt text you previously hand-wrote on Blogger.

Additionally, because WordPress themes rely on an explicit featured image layout concept that Blogger lacks, the Auto-Featured Images engine identifies the first image inside each imported post and instantly registers it as the official post thumbnail. This keeps your category archive grids, index pages, and social media sharing cards looking polished from day one.

What MigraSync Handles vs What You Still Do

MigraSync Automates This	You Still Handle This
Automatically detecting old Blogger image URLs in content	Ensuring you have enough allocated disk space on your hosting server
Safely downloading full-resolution source assets	Choosing your connection method (Live Blogger API vs Takeout ZIP)
Creating proper WordPress Media Library attachments	Auditing and verifying sample posts on the front end post-migration
Overwriting and updating your raw post content source paths	Handling structural theme/CSS adjustments for your new image sizes
Cleaning and normalizing legacy web filenames	Running a comprehensive full-site backup once verification is complete

Ready to Import Your Images Properly?

Do not leave years of visual content sitting indefinitely on Google’s CDN. Import your Blogger images securely into your WordPress Media Library during the core migration window, rather than treating it as an afterthought months down the line when old links begin to break.

Frequently Asked Questions

Does the default WordPress Blogger importer download images?

No. It copies post content with your original remote source URLs intact. You must use a separate media sideload utility or a dedicated migration suite to bring files over locally.

Will importing images slow down my migration?

The media ingestion phase adds time to the end of your workflow, directly proportional to your total image count and individual file sizes. Because MigraSync handles this in the background, you do not need to keep your browser window open.

Do I need to import images separately from posts?

Not when using MigraSync — a single migration run automatically threads your core text content and remote media attachments together. Manual, open-source workflows often require you to manage this in separate steps.

What about images embedded in static Blogger pages instead of posts?

Static pages are processed natively within the same migration pass. Any images discovered inside pages flow through the exact same media ingestion pipeline.

Can I import images without migrating my text posts all over again?

While possible using post-content scraping tools, re-running your migration onto a clean staging installation with media backup options turned on usually delivers a much cleaner final database structure.

Are my individual image files included in automatic SEO redirects?

No. Standard 301 server redirects map your legacy post and page URLs, not separate asset attachments. Your local media files will inherit clean paths under your local uploads directory; simply update your XML sitemaps to allow search engine bots to crawl them.

Does a Google Takeout export include all of my site’s images?

Yes, Google Takeout archives typically package your native media attachments inside the downloadable folder. MigraSync maps these local files straight into WordPress, reducing CDN download dependency. If an asset is missing from the local folder, the pipeline falls back to a remote CDN request to secure the file.