> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started/screenshots-in-transaction-test-views.md).

# Screenshots in Transaction Test Views

Up to 12 screenshots are visible in ThousandEyes test results, assuming that the transaction test completes successfully.

There is no limit to the number of screenshots that can be captured during a transaction. However, only the last 12 screenshots are shown in the test results on the ThousandEyes platform. The other screenshots are considered interim, and are discarded if the test completes successfully.

![](/files/RhefpmQluNAkhQJav7JZ)

What happens to the other screenshots? Why bother taking them if they aren’t saved? The reason is that interim screenshots can be very useful if your test encounters an error that stops the test from completing.

It can still be useful to specify additional captures in your transaction test script – because if the script encounters an error, you can inspect the state of the webpage leading up to the error. One screenshot will be automatically captured at the time the error occurs. If you had specified additional screenshots prior to the error point, those screenshots will also be available for inspection in the test results.

Use screenshots with **Console Logs** when you need both visual state and runtime evidence for the same selected run. Screenshots show what the browser displayed before or at the error, while **Console Logs** show browser, application, and script messages for the selected agent and round. Compare them for the same selected run, agent, and round. For the full transaction test troubleshooting workflow, see [Using the Transaction Test View](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-transaction-test-view#console-logs-tab).
