# Export the WordPress activity log as CSV: filters and the row limit

Download BetterShield’s activity log as a CSV: what the filters select, what each column holds, and how to spot the 10,000-row limit cutting it short.

By M Asif Rahman, Nov 11, 2026.

To export the WordPress activity log as a CSV with **BetterShield**, open **BetterShield › Activity › Site activity**, set the filters you want and select **Export CSV**. The file holds the rows those filters select, up to 10,000, with the time in both your site’s time zone and UTC.

The export is read-only and free. This post covers what the file contains, how to choose the rows that go into it, and how to recognize a file that stopped early. For what the screen itself records, read our post on the [WordPress activity log](/blog/wordpress-activity-log/); for a weekly routine that uses it, see [WordPress security monitoring](/blog/wordpress-security-monitoring/).

## Quick summary

- **Export CSV** on **Site activity** downloads the rows the current filters select, not the whole log.
- A file holds at most 10,000 matching rows.
- The columns start with **Time (site)**, **Time (UTC)**, **Event**, **Category**, **Severity**, **Who**, **About** and **Network**, then the raw record fields for scripts.
- If more rows matched than the file can carry, the screen says the result was limited and the last line of the file says it was cut short.
- Exporting never changes the log. The file can name accounts and networks, so keep it somewhere access-controlled.

## Why export the log at all

The Site activity screen is good for reading a few rows. A file is better when you want to keep a month of history before it ages out, hand a period to a colleague or a client, search it in a spreadsheet, or compare it against another record. A CSV is plain text with one record per line and commas between the fields, a format that [RFC 4180](https://www.rfc-editor.org/rfc/rfc4180) describes and that any spreadsheet opens.

The free plugin keeps activity rows for 30 days, so an export is also how you keep a period for longer, on your own terms. What you keep and for how long is your decision, which is why the file’s handling matters (see below).

## What the file selects

The export uses the same filters as the screen. Whatever the table shows is what the file is built from, so set the view first and export second.

The controls are the ones in our [filter and search guide](/docs/filter-activity-log/):

- **Category**: **All activity** by default, then **Sign-in & accounts**, **Public information about your site**, **Site settings**, **Updates & extensions** and **BetterShield itself**.
- **Search activity**: matches the actor, the target, the event name, an account login or an IP address within its stored network.
- **Filters**: **Who** (**Anyone** by default), plus **From** and **To** dates in the site’s time zone.

The page address keeps these choices, so you can copy it, open it later and land on the same view before you export again.

## What each column holds

The first eight columns are written to be read by a person.

| Column | What it holds |
|---|---|
| **Time (site)** | When the event happened, in the site’s time zone |
| **Time (UTC)** | The same moment in UTC |
| **Event** | The event, as the screen words it |
| **Category** | The area the screen files the row under |
| **Severity** | Critical, High, Medium, Low or Info |
| **Who** | The account or process behind the change |
| **About** | What the change was done to |
| **Network** | The network the request came from, stored truncated |

After those come the raw record fields, under their own names, for scripts and audits. You can ignore them when you are reading the file by hand.

Two columns are worth a note. Keeping **Time (UTC)** beside **Time (site)** means a file stays unambiguous when it is shared with someone in another time zone, or when your site’s zone changes later. And **Network** holds the truncated network BetterShield stores, never a full address.

## Set it up

1. Open **BetterShield › Activity › Site activity**.
2. Choose a category, type a **Search activity** term, or open **Filters** and set **Who**, **From** and **To**.
3. Check that the result count looks like the period you meant.
4. Select **Export CSV**.
5. Save the downloaded file in an access-controlled location.

If you already know the period you need, set **From** and **To** first. A narrow range is the easiest way to stay under the limit.

## The 10,000-row limit

A file carries at most 10,000 matching rows. For most sites that is far more than a month of activity, but a busy site, or a long date range can fill it.

When more rows matched than the file can hold, two things tell you:

- The screen warns that the result was limited.
- The last line of the CSV begins with `# truncated` and says that more rows matched than the export carries, and to narrow the date range and export again.

That last line is the one to look for. A file that ends in the middle of a period without that line is complete; a file that ends with it is not. Do not rely on a truncated file as a record of a whole period.

The fix is to export in smaller pieces. We recommend choosing date ranges small enough to stay below 10,000 rows, such as one week at a time, and saving each piece under its own name. Narrowing by category or by person also works when you only need one kind of event.

## From the command line

For a long range, or for a script, the command-line equivalent is `wp bettershield activity --format=csv`. Our [WP-CLI guide](/docs/wp-cli-commands/) lists its options. They include `--from` and `--to` as dates in the site’s time zone, `--area`, `--search` and `--actor`, and the CSV format exports every matching row.

```
wp bettershield activity --from=2026-08-01 --to=2026-08-15 --format=csv > august.csv
```

On a multisite network, the **Network Admin** screen has no export button. Use a single site’s own log, or the command line with `--sites=all`.

## What it can break, and how to undo

Exporting does not change the log, and there is nothing to undo on the site. The file is yours to keep or delete.

The file is the thing to handle with care. It can contain account names, network information and operational details about what happened on your site. Store it somewhere only the right people can open, send it to a colleague through a channel you trust, and delete it or keep it according to your own data policy. Our [privacy and personal data](/docs/privacy-and-personal-data/) page explains what BetterShield records about people.

## Check it is working

1. Open the CSV in a spreadsheet or a text editor.
2. Confirm that the first line names the columns above.
3. Compare the first and last records with the filtered view on the screen. They should match.
4. Check the last line. If it begins with `# truncated`, narrow the date range and export again.

## Recommended settings

We recommend exporting on a schedule you can keep, such as the first of the month for the month before, with the same date range each time, so that no period falls between two files and none is counted twice. Name each file with its range, keep them together, and open the last line of each one before you file it away.

If you export to share, narrow the view first so the file holds only what the reader needs. Fewer rows is easier to read and means fewer account names leaving the site.

## Frequently asked questions

### Does Export CSV download the whole activity log?

No. It downloads the rows selected by the filters on the screen, up to 10,000. Set a date range if you need a particular period.

### Which time zone are the times in?

Both. **Time (site)** is in your site’s time zone and **Time (UTC)** is the same moment in UTC, side by side on every row.

### How do I know the export was cut short?

The screen warns that the result was limited, and the last line of the file begins with `# truncated` and asks you to narrow the date range and export again.

### Can I export more than 10,000 rows?

The button stops at 10,000. Export smaller date ranges, or use `wp bettershield activity --format=csv`, which exports every matching row.

### Is there an export on the multisite Network Admin screen?

No. Use a single site’s own log, or `wp bettershield activity --sites=all --format=csv`.

### Is the CSV export part of the free plugin?

Yes. It is part of the free BetterShield plugin on WordPress.org, and the log keeps rows for 30 days.

## Conclusion

The CSV export is a quick way to take a period of the activity log out of WordPress. Set the filters, select **Export CSV**, and check the last line of the file for a `# truncated` note. If it is there, narrow the date range and export again.

BetterShield is free on [WordPress.org](https://wordpress.org/plugins/bettershield/). The reference page is [Export the activity log as CSV](/docs/export-activity-log/).
