How to Export Product Hunt Reviews and Comments (2026)

Product Hunt has no export button; developers can read launches and comments through the official Product Hunt API (GraphQL, with a developer token, and not for commercial use without Product Hunt's permission), and without code the InsightSocial Chrome extension exports either a product's reviews (rating, text, helpful votes, the team's reply) or a launch's full comment thread (upvotes, maker flag, replies nested with depth and parent) to CSV, Excel, JSON or Google Sheets. In our own runs in October 2026, a product returned 162 of its 162 reviews in 14 seconds, and a launch returned 212 of its 213 comments in 11 seconds.

TL;DR

Method	What you get	Cost	Skill
Product Hunt API v2 (GraphQL)	Posts and comments, as JSON	Free token; not for commercial use without permission	Code
Chrome extension (InsightSocial)	Reviews of a product, or every comment on a launch	Free up to 500 rows/month	None
Cloud scrapers (Apify actors)	Launches and products, many at once	Per result	Low

Reviews or launch comments: which one you want

Product Hunt has two kinds of feedback, on two kinds of page:

Reviews live on a product's reviews page (producthunt.com/products/<product>/reviews). They carry a star rating and, on many reviews, labelled answers to Product Hunt's prompts. They accumulate over the product's life.
Launch comments live on a launch (producthunt.com/posts/<slug>, or a product's launch page). They are the launch-day discussion: questions, feature requests, congratulations, and the maker's answers, nested as replies.

Founders usually want the launch comments the week of a launch (to answer and tag feedback), and the reviews for testimonials and competitor research.

Can you export them directly?

Not from the site. Developers can use the Product Hunt API v2, a GraphQL API that needs a developer token. Its documentation is direct about one condition: "The Product Hunt API must not be used for commercial purposes. If you would like to use it for your business, please contact us at hello@producthunt.com." (checked October 2026). If you are a company analysing your own launch, check with Product Hunt before building on the API.

What the export includes

Reviews: rating, review text (with the labelled answers kept as sections), reviewer name, date, helpful votes, the review type, and the team's reply as its own row under the review.

Launch comments: comment text, author, date, upvotes, whether the author is one of the makers, links written in the comment, and depth and parent so each reply sits under the comment it answers. Comments are read in Product Hunt's own vote order.

What the rows look like

Illustrative rows: the shape of an export, with made-up names and text, not real reviewers.

Depth	Parent	Author	Maker	Upvotes	Text
0		User A	No	14	Does it work with self-hosted instances?
1	User A's comment	Maker B	Yes	6	Yes, from version 2. There is a guide in the docs.
0		User C	No	9	Congrats on the launch! The onboarding is very smooth.
0		User D	No	3	Is there an annual plan?

For a product's reviews the columns are rating, text, helpful votes and date instead, with the team's reply as a row under the review.

Method 1: The Product Hunt API

Create an application in Product Hunt's API dashboard to get a developer token, then send GraphQL queries to https://api.producthunt.com/v2/api/graphql for a post and its comments, paging with the cursors the API returns, and write the CSV yourself. Keep the non-commercial condition above in mind.

Method 2: A Chrome extension

With InsightSocial's Product Hunt Scraper:

Install InsightSocial and sign in with Google.
Open the page: a product's reviews page for reviews, or a launch page for comments. The side panel says which one it found. No Product Hunt account is needed.
Allow Product Hunt once when Chrome asks.
Click Scrape. The extension reads the same data the page loads, including replies the page has not expanded, and keeps going in a background tab.
Export to CSV, Excel, JSON or Google Sheets.

Limits: one product or launch per run; a run stops at 5,000 rows or 2 minutes, far above what almost any launch or product has.

What it costs: scraping is free; exporting uses one credit per row. A launch with 300 comments fits inside the free plan's 500 rows a month; Pro is $9.99 a month for 10,000. Re-exporting rows you already exported is free.

Method 3: Cloud scrapers

Apify lists several third-party Product Hunt actors that collect launches by day or topic; the most used one cost $1.80 per 1,000 launches when we checked in October 2026. They suit tracking many launches over time rather than exporting one launch's discussion.

What founders do with a launch export

Answer everyone. Filter to top-level comments with no maker reply.
Tag feedback. Add a column for bug, feature request, pricing question or praise, then count.
Pull testimonials. Sort reviews by rating and helpful votes, then ask reviewers for permission to quote.
Benchmark competitors. Export a competitor's launch and compare the questions people asked.

Troubleshooting

"Product Hunt is showing a security check". Reload the page, let it finish loading, then start again.

A comment or two short of the count. The number Product Hunt shows can be slightly higher than the comments it serves; in our runs a launch returned 212 of its 213.

Wrong page type. A product's main page and its reviews page both work for reviews; for comments, open the specific launch.

FAQ

Can I export Product Hunt comments to CSV? Yes. Open the launch with a browser extension such as InsightSocial, or call the Product Hunt API with a token and write the comments out yourself.

Are maker replies included? Yes. Replies sit under the comment they answer, with a maker flag, so the thread reads the way it does on the page.

Are upvotes included? On launch comments, yes. Reviews carry the reviewer's rating and helpful votes instead.

Do I need a Product Hunt API key? Not with the extension. The official API needs a developer token.

Can I export every launch of the day? Not with InsightSocial, which reads one launch or product per run. Use the API or a cloud actor for lists of launches.