Blogging Tutorials

[WordPress] How to Serve Images from Subdomain

How to Serve Images from Subdomain

Want to improve your blog’s performance? Learn how to serve images from subdomain and dramatically improve speed of your blog on WordPress.

Hey there fellow bloggers! If you are serious about speeding up your blog, then you must have used tools like Pingdom and GTmetrix to test its speed. These tests usually show recommendations like serve images from subdomain, serve static content from a subdomain or from a cookieless domain or parallelize downloads across hostnames etc.

If you want to get rid of these flags in speed tests and want to speed up your blog, you should consider serving images from a subdomain. This is the easiest and completely free approach which helps in improving site load times.

In this article, I want to show you how to serve images from subdomain and improve page load time of your blog by reducing http requests from a single domain.

But, Why Serve Images From Subdomain?

Good question. In simple words, the number of connection a web-browser can make to a single domain is limited. Most modern browsers can make up to 6 connections per hostname at the same time.

Besides images, there are many things that loads from your domain. This includes scripts, CSS, JS, HTML, simple text files etc. A browser can’t load rest of the files from the same hostname until other files are loaded first. You can think of this as a queue.

This is why, you often read recommendations to use CDN services and other ways of improving site speed. Of course CDN services aren’t free. In such case, serving images from a subdomain is an effortless way of improving speed of your blog by some extent. This method can also be referred to as sharding.

Does Serving Images From A Subdomain Really Help?

Yes, it does. Images are one of the heaviest parts of any site. But they’re also one of the most crucial ones. For better SEO and to provide better understanding of your content, images are must-have.

A subdomain is considered as a separate website. By serving images from subdomain, it will take less time for a browser to load content from your server because the browser can simultaneously load content from different domains.

This significantly reduces the time a browser has to wait before it can serve all the content from your domain, dramatically improving load time of your blog.

I’m also serving images from a subdomain and you can checkout my blog’s speed ranking on Pingdom or GTmetrix before you continue.

If you are ready to learn how to serve images from subdomain, then keep reading.


  • Some knowledge of cPanel and phpMyAdmin.
  • Patience, a lot of patience.
  • Ability to keep calm if things don’t go out as intended.

Services Demonstrated in This Article

Note: Replace http:// with https:// everywhere in this guide if your blog has https certificate (like mine).

How to Serve Images from Subdomain?

Step 1: Creating A New Subdomain

To begin with, we will need a subdomain. To create a subdomain, log in to your cPanel and find Subdomains option. Click it to enter.

Creating Subdomain on SiteGround

Under Create a Subdomain, enter the name of your subdomain. You can choose any name that makes sense. For example, you can use img, images, media or anything of your choice. I’m choosing media.

Choose your domain from the drop-down list (of you have more than one) on which you need to create this subdomain. I will choose

Change the Document Root to your WP Content folder. By default, it’s public_html/wp-content/uploads if you never changed it.

Creating Subdomain in cPanel

Attention: If you changed the upload path in past for any reason, enter that path here. For example, you could have changed the wp-content/uploads folder to content/files. In this case, enter public_html/content/files under Document Root.

If you’re unsure whether you changed this path or kept default, then open an image from your blog and see the path. If it looks like, then you have the default path.

Now click Create and a subdomain will be created.

You now have a working subdomain. Great! So lets move ahead and tell WordPress to upload new images in the new location. Keep cPanel open. We will be coming back here.

Step 2: Changing Media Upload Path in WordPress

Log in to your WordPress dashboard and go to Settings > Media.

Under Full URL path to files, enter your complete subdomain including http://. I will enter Remember NOT to add any trailing slash (/) here.

Change Media Upload Path in WordPress

Save the settings.

If you can’t find the Full URL path to files option under Media settings, you can do this by entering a hidden WordPress options area. Enter your blog’s address in the following manner to access the options panel:

Once the options area is open, search for upload_url_path. Enter the subdomain here including http:// and without a slash at the end. I can enter here.

Change Media Upload Path in WordPress

Scroll down and save these changes.

Okay, so from now on, any new image uploaded to your blog will carry the new URL. If you upload image2.jpg, it will be available at

You’ve told WordPress about the new media upload path. Very well done. Now the next step is to change URLs of images in old blog posts to new ones. Keep reading on next page.

Step 3: Update Image Paths In Old Blog Posts

Your new images will now be uploaded to new address but what about old images? Your old articles still carry the old URLs to your images. This is why, you should change the references to images in old blog posts.

Of course you will not be editing your articles one by one manually. You just need to run a simple SQL query to make changes in all old blog posts.

For this, go back to cPanel and find phpMyAdmin and open it.

From the left panel, find and click the database of your blog. If you only have one site hosted under your hosting account, you don’t need to worry about this.

Find the SQL tab on top and click it. You will be presented with a white text area where SQL queries can be entered. Copy the following text, and paste it in the SQL area.

Copy This Query
UPDATE wp_posts SET post_content = REPLACE (post_content,’’,’’);

Replace subdomain with your subdomain and with the domain of your blog. I will change it to media and respectively.

Click Go to run the SQL query. It should show the number of rows updated.

If you face trouble running the query, you can also use find and replace option instead.

Select wp_posts table from the left pane, click Search, click Find and Replace. Now enter in Find and in Replace with. Select post_content in Column.

Find and Replace Query in phpMyAdmin

Now click Go to run the query.

After completing this step, you have updated image paths in old posts with new path. If your old post has an image say image3.png under, the URL to this image should be updated to reflect the new path. It should now show the new path as

Now there’s just one step to follow. We will now redirect old image paths to your new subdomain. Keep reading for this.

Step 4: Redirecting Old Image Paths to Subdomain

By following all steps above, you’ve not actually changed the directory in which your images are uploaded. You just changed the address where your images are served from. So your images are still being uploaded to wp-content/uploads directory and they can be accessed from there too. You can access image2.jpg from both AND

But if we keep serving the image from old URLs, then our purpose of serving images from subdomain is not fulfilled. Search engines like Google also has old locations of your images. This is why, we will be redirecting old image locations to their new location on subdomain.

For this, you will need to access .htaccess file in the directory of your WordPress installation. This is cpanelusername/pulic_html by default.

So go back to cPanel, find File Manager and click it to open. Check Show hidden files option and click Go. Now look for .htaccess file in the screen that just opened.

Show Hidden Files in cPanel

If you can’t find .htaccess file, you will need to create one. Click New File from the top panel and type .htaccess under file name. Click create and the new file will be created.

The .htaccess File Shown in cPanel

Now right click on the .htaccess file and click Edit. Copy and paste the following text in the file and save it.

Copy This
RedirectMatch 301 ^/wp-content/uploads/(.*)$$1

Make required changes to your subdomain and domain and save the file.

Now if you (or anyone else) try to access images using old path (, for example), it will be redirected to its new location ( automatically.

This will also help search engines recognize the new path to images of your blog.

Okay, every step needed to serve images from subdomain has been complete. Good work! It’s time to clear any cache you might be serving. Also go ahead and check your page speed score on Pingdom and GTmetrix. They should no longer show flags like Parallelize downloads across hostnames.

Serve Images from Subdomain: Summing Up

You pretty little enthusiastic thing! See what you did there? You just created a new subdomain and started serving images from it. By doing this, you dramatically improved your page speed score as well as load time. You should no longer see the recommendations to serve images from subdomain or from a cookieless domain.

Besides serving images from a subdomain, there are other steps you should take in order to improve your blog’s performance. You might want to read my article How I Supercharged My Blog to Score 90+ in Google PageSpeed for more information.

That’s it folks. This was Parvez on and you were reading How to Serve Images from Subdomain. I hope you found this article useful. If you have any question or if you get stuck somewhere, feel free to ask for guidance in comments. Also let me know if I missed something or if this article can be improved.

Until we meet next, happy blogging!

Support Me: If this article/tutorial helped you today, please consider supporting me and help me run
Anonymous VPN by Namecheap

Written By

Parvez Shaikh

I started blogging as a teenage hobby and decided to continue it after leaving my life as a System Admin behind. Now I juggle between being a tech blogger and a travel blogger/photographer. On Tech Stuffer, I share my views and knowledge about digital privacy, technology, gadgets, blogging etc. among other things.


  • Thank you for a great tutorial. I have do it and worked perfectly but not completely I still get the Parallelize downloads across hostnames Warning
    This I know is due to a directory of thumbnails for my Online Arcade Games Site that are not inside the uploads folder.
    How would I include these
    there’s a lot more of them

      • Generated by a plugin but these are from an old setup the current thumbs are put into the uploads directory.
        I have found a solution to move them into the uploads directory and change the posts image urls a lot of work so I will leave that for when I have free time.
        thanks for getting back to me.

  • For this, and my mistake if I missed it in the tutorial itself, but would the existing uploads directory have to be moved into the new sub domain so that past images work normally? Thanks.

    • I’m sorry for replying late and I hope you’ve found your answer already.
      You are not actually creating a new directory. You are keeping images in the same directory (wp-content/uploads) and just changing the domain to a sub-domain. So you will not need to move images anywhere.
      Just follow Step 3 and 4 so images are served from new location.

  • Hi Parvey,

    Thanks for the instructions and useful tips. I am trying to do the trick now but obviously on the latest WP version 4.9.8. I also use Siteground. I have created the subdomain without issues and changed the url upload path but I get a syntax error message when I try to run the SQL query, probably due to the newer version of SQL that i have.

    Also I realised then that some images are now randomly showing broken links. I reverted to the classic media path to fix this, but still keen to get this going. Could you assist please?


    • Hi Thomas.

      My blog used to run on SiteGround and now I’m using DreamHost. I am using the same setup as descibed in this post to serve images from a subdomain.

      I’m not sure if the newer version of SQL is causing the error because I recently ran the query without problem.

      I suggest you to take a look at the query for any breaks while copy/pasting.

  • Hello! I have two questions:

    1. Is this tutorial still up to date?
    2. Can I completely remove /uploads folder after completing this tutorial?

    Best regards,

    • Hi Kacper.
      Yes, the tutorial is up to date and working.
      You don’t actually remove /uploads directory. Your files are still uploaded to wp-content/uploads. What changes is the URL your files are served from.

  • Thank you!
    I already moved my images to subdomain, but I can’t replace old images. When I typed query in Phpmyadmin, this error showed up.: #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘://’,’http://subdomain.mysite.coml/media/’)’ at line 1
    Do you have any idea what I should do?

  • Make sure you are entering the path correctly. Look for possible spaces or typos.
    Also, why does your URL look like It should be simply

  • Sir it shows me error in Step 3: Update Image Paths In Old Blog Posts:
    #1064 – You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ‘://’,’’)’ at line 1

  • Hi, I could not open your site to check it. It looks like it”s under development or a new webiste. If it’s a new website, you don’t need to follow step 3 as you won’t have any images on the old path.

    Make sure there are no unneccessary spaces in the query or try to type it manually. Also, I am not sure how this works with MariaDB.

  • I’ve followed this tutorial and changed everything. The URL is pointing to my but I’m still getting 500 error and no files are displayed in WordPress too. The URLs are changed in the DB and redirect is done I see that the URL is pointing to the right subdomain. Can you please let me know what am I doing wrong?

    • Do you receive error 500 on your main domain or only on subdomain while trying to access files from the new path?
      Your new path should look like and the change has to be made in WordPress options area for the images to be displayed.

  • If you’re having problems with SQL syntax errors, change the single quote/apostrophe. When I copied and pasted it, the fancy version came over. I removed those and typed ‘ manually and it worked.

  • Hi Parvez,

    Thanks for sharing this post. This post is really helpful in serving images from Sub Domain.

    However I am facing a pecular issue with the end result. Mine is a new blog and no old Posts are there.
    Now the problem is, if I leave the option upload_url_path as blank, images are visible. But the image url is like

    If I give upload_url_path =, images are not visible in Media Library. Where as the images are there in backend, blank empty squares in library. While browsing permalink post only, points to

    What I have done so-far?
    1. Changed the file permission to 644/755.
    2. In WP Config I tried adding the following Line to change the default folder along with creation & changing Document Root path.
    define( ‘UPLOADS’, ”.’cdn’ );
    3. Installed & tried Force Regenerate Thumbnails plugin.

    Looking forward for your quick response.


    • Hi Vivek.
      Are you able to browse an image at If yes, then you should check the upload_URL_path. It should not have / at the end.
      It is possible that the subdomain does not have SSL certificate issued to it. In that case, issue it from cPanel and try to browse the image from subdomain.
      If both these things are already correct, upload a new image to library and see which URL it carries and open that link to see if that work.
      If all seems right, double check your setup and start over if needed.

  • Hi Parvez,

    I am able to resolve the issue.

    It wasn’t the issue of SSL or anything else.

    When I signed up for Cloudflare, I replaced the cloudflare DNS with my hosting provider DNS in my domain registrar. After 3 days or rigorous testing and resetting the all the 4 DNS(2 from Cloudflare & 2 from hosting provider) the issue was resolved.

    Thanks Again

Leave a Comment