Export a useful slice of evidence
Choose the right export route, narrow its scope, and verify the downloaded evidence without collecting more than you need.
For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.
On this page
You will have a useful CSV or JSON selection and understand its limits, time range and private-storage requirements.
Logged.ai → Activity → Events; Reports & exports → Exports
Available in Free and Pro with export permission on the selected site. Start with the question the file needs to answer and a UTC date range. Ordinary site downloads do not include another site’s records.
- A small date-based download: Reports & exports → Exports → Download now, up to 1,000 records and 2 MiB.
- The filtered Activity view: Activity → Export this selection, up to 500 matching records.
- A larger retained file: Prepare large export, or Create filtered background export from Activity, up to 1,000,000 rows and 256 MiB.
Pro saved reports and schedules are a separate workflow with separate storage and limits.
- For a small date-based file, open Reports & exports → Exports. Under Download now, choose CSV or JSON, From (UTC, inclusive) and Before (UTC, exclusive), then download.
- For person, object or other Activity filters, first refine the activity list. Open Export this selection and review its 500-record limit.
- For a larger selection, choose Prepare large export, or Create filtered background export from the filtered Activity view. Read the private-storage diagnostic before creating a job.
- For a background job, inspect its recorded state and download only when ready. A queued job is not a finished file.
Small direct downloads
Download now builds the complete matching result in memory. It needs no temporary export file, Sodium, Unix storage or cron. If the selection exceeds either limit, it is refused without a partial download; narrow the date range.
Fictional handover
To include 19 October 2026 in UTC, set From to 2026-10-19 and Before to 2026-10-20. Download a small CSV for a reviewer who needs a spreadsheet. If you only need one affected account, first apply that account’s Activity filter and use the filtered route instead of exporting everybody’s activity.
New saved background exports require PHP Sodium and store encrypted chunks in Logged.ai’s database tables. They expire after 24 hours and depend on WordPress scheduling; they do not require Unix filesystem permissions or writable upload directories. Keep the original WordPress authentication salts to read existing saved data. Older jobs may still use their original private file locations. Preserve those files and their original owner-only permissions until cleanup is verified; do not weaken the permissions.
Database and processing details
Both direct and saved workflows require compatible database behavior. Download now verifies privacy state using MySQL or MariaDB locking and InnoDB activity and privacy tables. A legacy MyISAM options table cannot provide that protection. Ask the host to review the diagnostic before any database change, with a reviewed backup.
Background membership is selected when its worker starts; membership and privacy are checked during bounded processing. Neither route promises a transactionally complete database snapshot. WordPress scheduling may delay a job. Native Windows has not been qualified for the saved-file workflow.
A background prerequisite is unavailable
Use Download now for a small enough date selection while the host reviews the missing prerequisite. The background diagnostic does not by itself disable activity logging or the direct route. Direct downloads can still refuse if their own database or size checks fail.
- Open the file in a suitable viewer and confirm the intended site, date interval, fields and relevant records. Export dates and content retain UTC.
- For a background export, retain its accompanying manifest where provided and note the job’s recorded state.
- Keep the file in a restricted location and send only the evidence the recipient needs.
- Deleting evidence in WordPress cannot recall a downloaded copy. Apply your organization’s retention policy to that copy separately.
If a job stays queued, use the background-processing checks. If a file is expired or no longer authorized, generate a new appropriately scoped export from evidence still available.
If a saved export fails verification
Before releasing a saved export, Logged.ai checks its metadata, encrypted chunks and complete bounded payload. Existing corruption or inconsistent records refuse output. If authority or content changes after streaming has begun, later bytes stop; bytes already received cannot be recalled and the download may be partial. Discard an incomplete file and prepare a new authorized export after resolving the reported issue.
Legacy export files on Windows
Automatic legacy-file cleanup cannot be verified on Windows. Logged.ai keeps those legacy jobs pending and stops delete-all uninstall before removing its tables. Ask your host to verify and complete the legacy cleanup outside the plugin, even if the old folders appear absent. New database-only jobs retain their database cleanup path. A cleanup warning must not be treated as proof that a file was removed.
This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.
Get help with your next step.