Menhly ToolsAll tools

YouTube Comments Scraper - Top, Newest & Replies

YouTube comments scraper, $0.30 per 1,000: public comments and replies with video metadata, numeric likes and parent thread links. Choose Top or Newest, download JSON or CSV, and keep raw display counts plus approximate dates. No API key, login or per-query fee.

This tool runs on Apify: pay only for the results you get, with a free monthly credit on new accounts.

Try it on Apify

For keyword search, channel uploads, Shorts and video metadata, use YouTube Scraper.

Export public YouTube comments and replies with video metadata on every row. Choose Top or Newest, get numeric likes alongside raw display strings, and link replies to their parent with parentCommentId.

This independent actor is not affiliated with or endorsed by YouTube or Google. No API key, login, cookies or account token is required.

Quick start

{
  "videos": ["dQw4w9WgXcQ"],
  "maxComments": 100,
  "sort": "top",
  "includeReplies": false,
  "language": "en"
}

Download the dataset as JSON, CSV or Excel. Use it for public feedback analysis, discussion research or your own monitoring workflow.

Input

Field Default Behavior
videos Required 11-character ids, youtube.com/watch URLs, youtu.be links, shorts URLs, m.youtube.com or music.youtube.com URLs. Up to 100 videos; duplicates removed by id.
maxComments 100 Maximum saved comments per video, from 1 to 100,000. Includes replies when enabled.
sort top top or newest parent-comment order.
includeReplies false Fetch reply pages and link them to parent comments.
language en YouTube UI language (hl), affecting labels such as relative publication times. English recommended for date parsing.

The daily Store example requests 20 top-level comments from one video, normally two JSON requests.

Replies and limits

The actor saves a parent-comment page, then opens its reply threads before moving to the next parent page. The same maxComments limit includes parents and replies. A large first thread can fill a small limit before later threads are opened. Reply order comes from YouTube and is not independently sorted.

Deduplication is by commentId within each video. Pagination uses separate top-level and reply continuations; reply tokens are not treated as the next parent page. If a later page fails, saved comments remain and a free terminal failure row explains the stop.

Output

One flat row per saved comment or reply. Missing strings are "", numbers 0 and booleans false. All keys are always present, never null.

Fields Meaning
inputIndex, input Original video input position/value.
videoId, videoUrl, videoTitle Normalized video metadata copied onto every row.
totalCommentsText YouTube's header count as displayed, not a promise of returned rows.
commentId, commentUrl, text Public comment identity, watch-page link with lc parameter and text.
authorName, authorChannelId, authorChannelUrl Public display name and channel link.
isCreator, isVerified Whether YouTube marks the author as video creator or verified.
likeCount, likeCountText Numeric interpretation and raw displayed likes, including rounded K/M abbreviations.
replyCount, replyCountText Displayed reply count and its raw string.
isReply, parentCommentId Reply flag and parent id; parent id is empty for top-level comments.
publishedTimeText YouTube's relative time label, preserved exactly.
publishedAtApprox, isEdited Approximate UTC ISO date, and whether the label contains (edited).
sort Requested parent-comment sort.
status, subStatus, error, scrapedAt Result status, machine-readable detail, error and UTC ISO collection timestamp.

Dates and counts are approximate

YouTube supplies relative labels such as "7 years ago", not an exact comment timestamp. publishedAtApprox is calculated from scrape time. Months use 30 days and years 365 days, so it is suitable for rough ordering, not exact chronology. Unrecognized localized labels leave publishedAtApprox empty; publishedTimeText is always retained.

Like counts are rounded exactly as YouTube displays them: 70K becomes 70000 and 1.2M becomes 1200000. This does not recover an undisplayed exact count. Missing or unsupported count labels use 0 with the original string retained.

YouTube's header count may include comments that its public feed does not expose. The actor can return fewer than requested even when the header is larger. A platform spike requested up to 500 top comments on each of three videos and returned 500, 500 and 370; the recent video's continuation ended despite a larger header count.

Pricing and statuses

One comment event per saved successful comment or reply. FREE $0.0003, BRONZE $0.00025, SILVER $0.0002, GOLD and above $0.00015 per row ($0.30 / $0.25 / $0.20 / $0.15 per 1,000). Replies have the same price.

Standard Actor start fee: $0.00005 per GB, minimum one event. There is no per-query fee or separate reply surcharge. Failed and empty rows have no comment charge; the start event still applies. No extra dataset-item event.

The actor saves a page batch before charging and honors the event spending cap.

status / subStatus Comment charge
ok / comment Yes
no_comments / comments_disabled No; video exists but has no comment continuation
no_comments / empty No; comment feed returned no visible comments
failed / invalid_input, not_found No
failed / http_CODE, blocked, parse_error, network_error No
failed / free_work_limit No; internal unpaid-work guard stopped collection
failed / cost_limit_reached No; event spending cap reached

Honest limits

API examples

curl -X POST \
  "https://api.apify.com/v2/acts/sumitr_mardy~youtube-comments-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"videos":["dQw4w9WgXcQ"],"maxComments":20,"includeReplies":false}'
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("sumitr_mardy/youtube-comments-scraper").call(
    run_input={"videos": ["dQw4w9WgXcQ"], "maxComments": 20}
)
for comment in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(comment["text"], comment["likeCount"], comment["parentCommentId"])

Use it from AI agents (MCP)

Hosted OAuth clients can sign in through Apify MCP:

{"mcpServers":{"youtube-comments":{"url":"https://mcp.apify.com/?tools=sumitr_mardy/youtube-comments-scraper"}}}

Bearer clients can use local secret configuration:

{"mcpServers":{"youtube-comments":{"url":"https://mcp.apify.com/?tools=sumitr_mardy/youtube-comments-scraper","headers":{"Authorization":"Bearer <YOUR_APIFY_TOKEN>"}}}}

For stdio clients with Node.js:

{"mcpServers":{"youtube-comments":{"command":"npx","args":["-y","@apify/actors-mcp-server","--actors","sumitr_mardy/youtube-comments-scraper"],"env":{"APIFY_TOKEN":"<YOUR_APIFY_TOKEN>"}}}}

Agent tips: begin with 20 comments, check status, distinguish raw counts and approximate values, and use parentCommentId when rebuilding threads. Configure your own schedule for recurring monitoring and deduplicate by videoId + commentId.

Support: Actor issues.

For public channel profiles, subscriber/view totals, creator links, keyword discovery and recent upload activity, use YouTube Channel Info Scraper. Business email is a prompt-presence boolean only; no addresses are revealed.