
Blogger documents two separate backup workflows. A content backup is the file Blogger tells you to use when importing posts, pages, and comments. A theme backup is a saved copy of the blog’s theme, accessed from the Theme area. Make both before changing a theme or moving content, because Blogger describes them as different files for different jobs.
The distinction matters when a blog has years of posts but a recently customized layout. Saving only the theme does not follow Blogger’s documented import path for posts, pages, and comments. Saving only the content does not replace the documented step for downloading the current theme.
Content backup: the file for posts, pages, and comments
Blogger says you can back up blog content with Google Takeout. The workflow starts by using the Google account that administers the blog. Blogger also provides a route inside the dashboard: choose the blog, open Settings, then under Manage blog select Back up content and Download.
The resulting Takeout archive contains material Blogger describes for content backup. When you later want to import content into a blog, Blogger identifies one file by name: feed.atom. Its instructions say to open the Google Takeout backup, choose Takeout Blogger Blogs, open the directory for the blog you want to import from, and locate feed.atom.
That filename deserves attention. Blogger does not tell readers to select the whole Takeout archive during import. It says to upload the feed.atom file found inside the archive. For older exports, Blogger says its historic backup.xml files can be imported in the same way.
Blogger’s documented import screen sits under Settings. Select the destination blog, choose Manage Blog, then Import Content and Import. From there, select the feed.atom or .xml file stored on your computer and open it.
The documentation names three types of imported material: posts, pages, and comments. It does not say that this import is a complete restoration of every part of a blog. That limit is worth keeping in view. A content backup has a clearly documented role, but the cited instructions do not establish that it captures every image, setting, or design detail.
Theme backup: the file for the blog’s look
A theme backup follows a separate route. Blogger’s content-backup help page tells users to select the blog, open Theme, use the arrow beside CUSTOMIZE, choose Backup, and then select DOWNLOAD in the dialog.
Google’s theme help page describes the same purpose in plain terms: themes change how a blog looks and how visitors can view and interact with it. That page gives a closely related path: select the blog, open Theme, then choose More, Backup, and Download. The exact icon label can vary between the two help pages, yet both point to the Theme section and a Backup download action.
This is the backup to save before applying another theme or making design changes you may want to reverse. Blogger’s theme documentation says that the Theme area is where you choose a theme, apply it, and customize settings such as background images, column widths, fonts, colors, and text size. A saved theme copy belongs to that design workflow.
The content backup and theme backup therefore answer different questions:
| If you need to preserve or move… | Blogger’s documented workflow |
|---|---|
| Posts, pages, and comments | Back up content with Google Takeout, then import feed.atom or an older .xml backup file |
| The current blog theme | Open Theme and download a theme backup |
The table does not mean each file contains only the items listed beside it. It reflects what the cited Blogger pages explicitly document: the import instructions for content name posts, pages, comments, feed.atom, and older XML backups; the Theme instructions describe downloading a copy of the theme.
Why both backups are sensible before a theme change
Changing a theme concerns the appearance of the blog. Blogger’s theme help page says themes affect the way people view and interact with a blog. It also places customization controls in the Theme section. That makes a theme backup the relevant saved copy before experimenting with a new design.
Posts and pages are different content objects. Blogger places their backup under Settings and routes users to Google Takeout. Its import instructions then direct users to feed.atom or a historic Blogger .xml file. A theme download is not named in those instructions for importing posts, pages, and comments.
Take a fictional example. A blogger plans to try a new layout on Saturday. The blog already has published posts, several standalone pages, and reader comments. The cautious sequence follows Blogger’s two documented workflows: download the content backup through Settings and Google Takeout, then download a copy of the current theme through Theme. If the blogger later needs to import posts, pages, and comments into a blog, Blogger’s directions point to feed.atom from the Takeout archive, or to an older compatible XML backup.
The example does not prove what either file contains beyond Blogger’s instructions. It simply keeps the two procedures separate, which avoids a common mix-up: treating a theme download as the file to import content from.
Importing content without publishing it straight away
Blogger includes a publishing choice during import. On the Import Content screen, there is an option labeled Automatically, publish all imported posts and pages. Blogger says to turn that option off if you do not want imported content published automatically.
This setting matters when importing into a blog that visitors can already see. It gives the person running the import a documented choice about whether imported posts and pages publish automatically. Blogger’s wording refers to posts and pages in this option. The cited page does not spell out a separate publication rule for comments.
A practical reading of the workflow is simple: locate the correct content file first, then check the automatic publishing choice before selecting it. The file-selection stage and the publication setting are both part of Blogger’s stated import path.
Blogger also says that imports have a daily limit on the number of files, while it states there are no file-size restrictions. That is a limit on the number of files imported in a day, not a claim about how long an import will take or whether every archive arrangement will behave the same way.
What these help pages do not establish
Backup language often invites broad promises. The two cited pages do not support them here.
They do not say that a content backup captures every image associated with every post. They do not say that a theme backup recreates every account-level setting. They do not describe a one-click, complete restoration of all possible blog material. They also do not state that importing a content file will reproduce a theme’s appearance.
Those gaps do not make the documented backups useless. They define the safe wording. Blogger gives a content workflow, names the file to import for posts, pages, and comments, and gives a separate workflow to download the theme. That is the documented ground to stand on.
Keep the original downloads in a place you can find later. When working with a Google Takeout archive, identify the blog directory and feed.atom before beginning an import. When working on design, download the current theme from the Theme section before applying or customizing another one. These are two different preparations for two different kinds of change.
A short pre-change check
Before you alter a theme, confirm that you have completed both downloads. First, use Settings > Manage blog > Back up content > Download and obtain the Google Takeout content backup. Second, use Theme > Backup > Download to save the current theme copy.
Before moving posts, pages, and comments to another Blogger blog, open the Takeout archive and find feed.atom in the relevant blog directory. If you have an older Blogger backup, Blogger says a .xml file can follow the same import route. At import time, decide whether imported posts and pages should publish automatically, then set the option accordingly.
The useful question is not which single file “backs up Blogger.” Blogger’s own documentation separates the tasks. Content backup supports the documented import of posts, pages, and comments. Theme backup saves a copy of the current theme. Keeping both downloads gives you the files Blogger identifies for those separate workflows.
Are you changing the blog’s look, moving its written content, or doing both? If you are importing content, have you found feed.atom and checked whether automatic publishing should stay on?