A post rarely travels alone: it has a featured image, pictures in the text, maybe a gallery, a cover image or a PDF to download. When you push a post to another WordPress site with Content Sync in Import Export by RockStarLab, these files go with it. Below is exactly which media is copied, what happens to alt text, captions and image sizes, how duplicates are avoided, and what stays behind. We checked it with one test post that used every kind of media, pushed from a staging site to a live site.
Free: Content Sync with media for posts and pages, and Media Library sync. PRO: the same for custom post types and WooCommerce products, including product galleries.
Short Answer
- The featured image, images in the text, gallery and cover images, and files the post links to (PDFs, File blocks, videos, audio) are uploaded to the other site’s Media Library together with the post.
- Addresses in the text are changed to the new files, and block image IDs point to the new Media Library items.
- Alt text, caption and title of each file are copied; image sizes are created by the target site.
- Files that already exist on the target site, even under another name, are reused instead of uploaded again.
- Images hosted on other domains (a CDN, a partner’s site) are left as links.
The test post
On staging, the post “New Bakery Menu” had:
- a featured image with alt text, a caption and a title;
- a Cover block with a background image;
- an Image block (a croissant photo);
- a Gallery block with two images;
- a link to a PDF price list in the Media Library;
- an image from another domain,
images.example.org.
Before the push, we uploaded the same croissant photo to the live site under another name, menu-croissant.jpg, to see whether it would be uploaded twice.
The push itself is the usual one: select the post on Posts, click Sync Content, choose the live site, click Push to Site, check the pair in Map Posts for Sync, and click Confirm & Sync. Media needs no extra setting.

What arrived on the live site
| Media in the post | On the live site |
|---|---|
| Featured image | Uploaded, set as featured image and attached to the post; alt text, caption and title copied |
| Cover block background | Uploaded; the block’s image address and ID point to the new file |
| Image block (croissant) | Not uploaded: the identical file menu-croissant.jpg already on live was used |
| Gallery block, 2 images | Both uploaded; the gallery shows them in the same order |
| PDF link | PDF uploaded; the link points to the copy on the live site |
| Image from another domain | Unchanged: still loads from images.example.org |

The live site created its own thumbnail sizes for every uploaded image, including the sizes its theme and WooCommerce register, so images fit the live site’s layout even if staging uses another theme.
Pushing again doesn’t duplicate files
We pushed the same post again through an AI agent. The live Media Library kept the same number of files: each source file was matched to the copy made by the earlier push. The plugin recognizes files by their contents, not by name, which is why the croissant photo was matched to menu-croissant.jpg. The same check is used by imports; see media files without duplicates.
One consequence: when a file is reused, the live copy keeps its own alt text and caption. In our test, menu-croissant.jpg on live had no alt text and still had none after the push, while the alt text written in the Image block of the post was copied with the post text. If alt text matters for a reused image, edit it in the live Media Library once.
What stays behind
- Images on other domains. A CDN address or an image on a partner’s site is not downloaded. If that domain stops serving the file, the image breaks on both sites.
- Files that aren’t used by the post. Content Sync copies media that belongs to the posts you push. To copy a set of files on its own, select them in Media → Library (list view) and use Sync Content there, or see importing Media Library files.
A push adds files to the target site and changes posts there. Before syncing many posts to a live site, create a backup of it.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) pushes media the same way. A prompt on the staging site:
Push "New Bakery Menu" to the live site, updating the existing post,
and tell me which media files were uploaded and which already existed.
In our run, the agent started rsl-ie/sync-push-start with the mapping {"4098": 2025} and read the result from rsl-ie/sync-job-status: 1 post updated, images_synced: 6, and an image_map that paired each of the six staging files (five images and the PDF) with an existing file on live. The live Media Library count didn’t change.
FAQ
Does Content Sync copy the featured image?
Yes. The file is uploaded to the target site, set as the featured image and attached to the post, with its alt text, caption and title.
Are images in galleries and Cover blocks copied?
Yes. In our test, the Gallery, Cover and Image blocks pointed to the new files on the target site after the push.
Are PDFs and other linked files copied?
Yes, when they are in the Media Library of the source site: a link to a PDF, a File block, a video or an audio file is copied with the post and the link is changed.
Will pushing a post again upload its images again?
No. Files that already exist on the target site are found by their contents and reused, even if they have another name there.
Are images from a CDN or another domain downloaded?
No. Only files from the source site’s Media Library are copied; other addresses stay as they are.
Related Guides
- How Content Sync Works: API Keys, Push, Pull and What Gets Copied
- How to Export and Import WordPress Media Files Without Duplicates
- Import WordPress Media Library Files
- Sync Files in Any Folder with the WordPress Media Library
Get the free plugin on WordPress.org.

Comments 0
Have a question or a tip to share? Leave it below.