How do I export findings to CSV?

Steps

1. Click Issues in the sidebar.
2. Optionally narrow the list first, if you want only part of it in the file. You can use the search box, the Severity, Confidence, Class and Target dropdowns, or the triage chips.
3. Click Export CSV, at the top right of the page, next to Export JSON. One click starts the download.
4. Open the downloaded file in a spreadsheet tool. Compare its row count with the list on screen, and note any gap.

Good to know

Use CSV for a spreadsheet, a ticket import or a quick pivot by class or target, and most teams start there because anyone can open the file without special tools. Choose JSON instead when a script will read it. Our page on exporting JSON shows that button.

An API route does the same job. It is GET /api/export/issues. It returns JSON or CSV and accepts filters, and it needs the issue:export permission. The in-app screens do not show whether the button follows your current filters. Test it yourself: export once with a filter switched on, then count the rows in the file.

Question	Answer
Where is the button?	Top right of Issues
Which formats?	CSV and JSON
What permission?	Issue export
Other CSV exports?	Targets and the scan Sitemap

• No buttons on the page? Your role may lack the permission. See why you cannot export issues.
• Does the file look short? A short file can come from a filter you forgot about, or from access that limits which targets you can read. Read why a CSV export is partial.

The export tutorial goes further. Questions? Contact us.

Related questions

• How do I export findings as JSON?
• Why can't I export findings?
• Why does my findings export include only some of my findings?
• How do I export a scan's sitemap?
• How do I export my list of targets?

Full tutorial

How to export vulnerability findings to CSV or JSON

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre