Join our Discord
BrowserStack Load Testing test data retention
How long are the test data, test results, and media retained based on your plan, and how to export what you need.
BrowserStack Load Testing retains all your test data for a set period based on the plan you have opted for. This page explains exactly how long each type of data is retained, what stays available afterward, and how to export anything you want to keep long-term.
Retention is the same across all available test types and across all regions.
How long does Load Testing retain my data
Your data falls into three categories, each with its own retention period.
Test results and reports
Dashboards, performance metrics, VU/VUH results, threshold and assertion outcomes, AI insights, and reports you export are retained for a period that scales with your plan:
| Plan | Retention period |
|---|---|
| Free | 30 days |
| Essentials | 90 days |
| Pro | 1 year |
| Enterprise | 2 years |
The period is measured from the date each test run completes.
Test inputs
Files you upload to run a test: test scripts, .jmx files, and test-data files (such as CSVs). These follow the same plan-based schedule as your results, but the clock is measured from when the input was last used in a run:
| Plan | Retention period |
|---|---|
| Free | 30 days |
| Essentials | 90 days |
| Pro | 1 year |
| Enterprise | 2 years |
The clock resets each time an input is used in a new test run. A script you rerun regularly is retained for as long as you keep using it. One you stop using is removed once the period above elapses from its last run.
Session media and logs
Session recordings (video), network logs, and per-session browser-test logs are kept based on your plan tier:
| Plan | Retention period |
|---|---|
| Free | 15 days |
| Essentials, Pro, Enterprise | 30 days |
The period is measured from the date the test run completes.
What happens after the retention period
When data reaches its retention period, only the underlying data expires. Your test run history stays. You’ll still see that the run happened, along with its high-level record, in the Test Runs dashboard. What’s removed is the detailed data for that run: its metrics and charts, exportable reports, session video, network logs, and any expired input files.
If you open a run whose data has expired, the detailed results, media, or downloads for it are no longer available.
Export your data before it expires
To keep results, reports, or recordings beyond your plan’s retention period, download them while they’re still available:
If you need long-term history for trend analysis, export results on a schedule (for example, as a step at the end of your CI pipeline) so you always have a local copy.
Frequently asked questions
Does retention change if I upgrade or downgrade my plan?
Yes. When you upgrade, new and existing data is retained for the longer period that your new plan allows. When you downgrade, retention shortens to the new plan’s window, so data older than that window becomes eligible for removal.
What counts as "last used" for a test input?
An input is considered used whenever you include it in a test run. Its retention clock resets to that run’s date, so scripts and test-data files you use frequently stay available as long as you keep running them.
Is retention different in different regions?
No. The same retention periods apply regardless of the region your tests run in.
Does data retention affect my VU-hour usage or billing?
No. Retention controls how long test data is stored. It has no effect on VU-hour consumption or billing. See How VU Hours (VUH) are calculated.
Need help?
If you have questions about data retention or need data restored, contact BrowserStack Support.
Related pages
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!