Back to blog
6 min read Export Guides

WordPress CSV Posts Export: Export Blog Posts to CSV, Excel, JSON, XML, and ODS

WordPress’s own export writes XML for another WordPress site; for a spreadsheet you need CSV or Excel. In Import Export by RockStarLab → Export, select Blog Posts and choose which posts and columns go into the file. CSV suits a file you will map into another system, XLSX opens directly in Excel.

Start with the question your file needs to answer. An editorial inventory usually needs a title, slug, status and date. Moving articles to another site also calls for the original body, excerpts, taxonomy terms and any custom fields the destination uses.

1. Select Blog Posts

Open the export wizard in WordPress admin, choose Blog Posts and click Next Step. Pages, products and custom post types have separate selections. If you only need a list of public links across the site, use the site URL export instead.

Blog Posts selected as the WordPress export content type
Choose Blog Posts to work with ordinary WordPress posts.

2. Export all posts or select a subset

Leave the filters empty to include all available posts. For a public content inventory, add Status → Equals → publish. An unfiltered file can include drafts, even when their titles never appear on the blog.

For a hand-picked set, choose Add Filter → ID → In and enter the numeric post IDs separated by commas. You can find a post’s ID in its edit URL after post=. Check Total Items Available before moving on. For a contributor handoff, select Author Email instead. For more combinations, see the export filter examples.

Post ID filter with four comma-separated values
Use ID and In to select individual posts in one export.

3. Choose what goes into each row

In Select Fields, build the export file structure from the available fields. Each post gets a row in CSV. Use Add all beside an individual group when you need that whole group. For an editorial spreadsheet, keeping only the columns an editor will read makes the file easier to use.

WordPress post export structure with selected field groups
Add the fields your spreadsheet needs from the groups on the right.
Purpose Fields to include What to expect
Identify a post ID, title, slug, status, date An ID identifies a post on the source site. Keep the slug as a second reference when moving between sites.
Preserve article content Content and excerpt The body contains stored markup, including HTML tags and Gutenberg block comments. The excerpt is a separate field and can be empty.
Retain categories and tags Taxonomies → category and post tag A CSV cell can contain a JSON list of terms with names, slugs and parent paths. A post with multiple tags still occupies one row.
Identify a featured image Featured image URL, ID, title and caption The URL points to the image file. The attachment ID belongs to the source site. An image embedded only in the body can appear in the HTML even if the featured image column is empty.
Include custom editorial data Custom Fields or ACF Fields Select the registered fields needed by the destination. A text field can be read directly, an ACF image can contain a URL, and a Repeater can contain an array of subfield values.

For example, a travel guide might have a subtitle, cover image and a list of stops. Export the subtitle for a human-readable report. Include the Repeater when the destination also needs each stop’s name and duration. Keep that cell intact when transferring the data. If you need a separate inventory of attachments, follow the Media Library export guide. For an SEO audit, select the relevant metadata using the Yoast title and description guide.

4. Choose CSV, Excel, ODS, JSON or XML

Choose CSV when the destination expects delimited text. Keep the header row enabled and agree on the delimiter with the recipient. Choose XLSX for Excel, ODS for an OpenDocument spreadsheet, or JSON or XML when another application expects that format.

CSV options with header row and export filename
Keep the header row so each column can be identified during import.

Enter a filename without the extension. Keeping {job_id} in the name helps distinguish successive runs. Click Start Export. When the job finishes, compare Items Exported with the expected count, then click Download Export File. Enable Download as ZIP if you want a compressed download.

Completed post export with the file ready to download
Check the item count before downloading the file.

5. Read the file before handing it off

Open CSV using the spreadsheet application’s text import dialog if everything appears in one column. Select the delimiter used during export and UTF-8 for multilingual titles. A post body can contain quotation marks, commas and line breaks. Use a CSV reader that respects quoted cells rather than counting text lines to determine how many posts you have.

Pick one post you recognize. Compare the title and slug with its edit screen, open its featured image URL, and look for a known term in the taxonomy column. For a migration, keep the original download and follow the WordPress post import and field mapping tutorial on the destination.

Export posts with an AI agent

Connect your agent using the WordPress Abilities API setup guide. Specify the site, selection, fields and format in your prompt. For example:

On the connected WordPress site, prepare a CSV inventory of published blog posts. Include ID, title, slug, date, categories and tags. Inspect the post export schema and preview the selection first. Tell me the proposed columns before starting.

Export the posts with IDs [insert your IDs] to XLSX. Include their original content, featured image URL and the registered ACF subtitle field if available. Run the export, wait for completion, and return the download link, processed count and failed count. Leave the posts and settings unchanged.

The agent can inspect the available fields with rsl-ie/get-content-schema, preview with rsl-ie/export-preview, submit the job with rsl-ie/export-start and check the result with rsl-ie/job-get. A pending job still needs to finish before the file is ready. For a recurring report, see how to schedule repeated exports.

Video walkthrough

The video shows an earlier version of the export interface. Use the screenshots above for the current field picker and format settings.

FAQ

Can I export WordPress posts to CSV?

Yes. Import Export by RockStarLab lets you export WordPress blog posts to CSV, including selected post fields and available custom fields.

Can I filter posts before exporting?

Yes. You can use filters such as author email, title, date, status, and other available fields to export only specific posts.

Can I export ACF fields with WordPress posts?

Yes. If Advanced Custom Fields is installed and fields are registered for the selected post type, ACF fields can be selected for export.

Can I export ACF Repeater fields?

Yes. ACF Repeater field data can be included in the export file when available for the selected post type.

Which export formats are supported?

The plugin supports CSV, JSON, XML, XLSX, and ODS export formats. You can also download the export file as a ZIP archive.

Dmitriy
About author

Dmitriy

WordPress Developer with 15+ years of commercial experience. Elite Author on ThemeForest and creator of custom WordPress plugins. Passionate about clean code, performance optimization, and building useful tools for the WordPress community.

JOIN THE CONVERSATION

Comments 0

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

Leave a comment

Your email address will not be published. Required fields are marked *

We store your name, email and comment to show and moderate it; your email is never published. Spam protection is provided by Cloudflare Turnstile and profile pictures by Gravatar. See our Privacy Policy.


Try the plugin with no risks!

New users get 1 month with access to all premium features. Experience the most powerful WordPress data engine today.

Download Now
Get PRO for FREE