How to Export Trustpilot Reviews to CSV (2026 Guide)

Trustpilot shows reviews page by page, and a company profile has no “download to CSV” button. If you need those reviews in a spreadsheet, for e-reputation work, competitor research, or a platform migration, the default path is copy-pasting them one at a time. This guide covers the faster routes, what data is actually available, and the traps that quietly produce a broken file.

What a Trustpilot review actually contains

Before exporting anything, it helps to know what a single review holds. On a company page (trustpilot.com/review/{domain}), each review carries:

• A star rating from 1 to 5
• A title and the body text, which can run to several paragraphs with line breaks
• The date of the experience being described
• The date the review was published, which is often different
• The reviewer’s display name and country
• The language the review was written in
• Whether Trustpilot flagged it as a verified experience
• The company’s reply and the date it was posted, when there is one

That last pair matters more than people expect. If you are studying how a business handles criticism, the reply rate and the delay between a one-star review and its answer tell you more than the average rating does.

Option 1: the built-in exports, if the business is yours

If you own the Trustpilot profile, start here. Trustpilot’s paid business plans include review exports for your own business, and its API serves approved integrations. This is the cleanest route: it is sanctioned, it gives you your own data, and nothing breaks when Trustpilot redesigns a page.

It has two limits. It only covers your own profile, so competitor research is out. And it sits behind a business plan, which is a real cost if exporting reviews is the only thing you need.

Option 2: copy-paste

It works. For twenty reviews it is arguably the fastest thing you can do.

It stops working around the fifty-review mark, and it fails in a specific way worth naming: pasting multi-paragraph review text into a spreadsheet breaks the row structure, because the line breaks inside a review are read as new rows. You end up with a file that looks plausible and is quietly wrong. If you go this route, paste into a plain text editor first and clean it up before it reaches the spreadsheet.

Option 3: a browser extension

A browser extension reads the page you already have open, in your own session, and writes the file locally. This is where most people land for competitor pages or large profiles.

The steps:

1. Open the Trustpilot company page you want, for example trustpilot.com/review/example-shop.com.
2. Open the exporter’s side panel. It should recognise the page and show you the company name and how many reviews Trustpilot announces.
3. Set filters if you need them. Trustpilot itself supports filtering by star rating, by language, and by keyword search, so those can be applied at the source rather than after the fact. It does not expose an arbitrary date range, so a tool that offers one is either filtering locally after downloading everything or promising something it cannot do.
4. Start the extraction and watch the preview fill in. This is the moment to check that the data looks right, before committing to anything.
5. Export to CSV, Excel or JSON.

ExportReviews’s Trustpilot exporter does exactly this, and the first 25 exported rows are free without an account.

The four things that make an export good or useless

Pagination that finishes. A profile with 3,000 reviews is 150 pages. An exporter that gives up after page 10, or that silently stops when a request fails, hands you a file that looks complete and is not. Look for a visible count against the announced total.

Deduplication. Trustpilot reorders reviews as new ones arrive. If a review moves from page 3 to page 4 while you are exporting, a naive tool records it twice. Duplicates are worse than missing rows, because they skew every average you compute afterwards.

Dates you can sort. A review dated “2 months ago” is useless in a spreadsheet. A good export normalises dates to a standard format like 2026-06-14 while keeping the original wording in a separate column, so nothing is lost if the conversion is imprecise.

A CSV that survives contact with a spreadsheet. Review text contains commas, quotation marks, emoji and line breaks. All four break naive CSV writing. The file must quote fields properly and preserve line breaks inside quoted cells, or a 3,000-row export becomes 4,500 malformed rows in Excel.

What to do once you have the file

The first pass is almost always the same: sort by rating, read every one-star and two-star review in order, and tag the recurring themes by hand. Twenty minutes of that beats any sentiment score, because the value is in the specific complaint, not its polarity.

After that, the columns start earning their place. Group by month to see whether a problem is getting better or worse. Filter by country when a complaint pattern is regional, which for shipping issues it usually is. Compare the reply column against the rating column to find the reviews nobody answered.

Doing this responsibly

Exported reviews are public content, but they are attached to real people. Two habits keep you on solid ground: do not republish reviewer names, and do not use an export to build a profile of individual reviewers. Pace your requests rather than hammering the platform. And if you plan to display collected reviews commercially, or to process them at scale, get legal advice for your jurisdiction, because platform terms and data protection rules both apply and both change.

There is a longer discussion in the legality of exporting Trustpilot reviews.

Which format to pick

Short answer: CSV if the file is going into a spreadsheet or a database, Excel if you want the metadata sheet and column widths handled for you, JSON if code is going to read it. The formats comparison goes into the specifics, including the separator problem that turns a perfectly good CSV into a single column in a French or German Excel.