Why exported comment counts differ from the app

The platform count is a total, not a promise

The number under a video in the app is a platform-side total. It can include replies as well as main comments. It can include comments that were later removed, hidden by the creator, filtered by TikTok, or posted from accounts that are no longer accessible. It is updated on the platform's schedule, not yours.

GlimTok shows this number as reported, labelled as a reported count. It is useful context. It is not a description of what any tool can retrieve, and no honest export tool should present it as one.

The retrieved count is what you actually have

When you load comments in the viewer or run an export, GlimTok counts what came back. Main comments and replies are counted separately, because they are separate rows and often separately priced. A retrieved count of 20 main comments after one page means exactly that: one page, twenty records.

Duplicate IDs are removed. If a reply sample shown beside a comment overlaps with the full thread you loaded later, the overlap is counted once. Adding page lengths together will therefore overstate what you hold; trust the retrieved counts on the page or in the report.

The accessible count is unknown, and that is fine

There is a third number nobody can show you: how many comments a source could return if it paged to the end. It depends on the source's access, on rate limits, on the video's settings and on the moment. GlimTok does not estimate it. Instead it tells you why loading stopped, which is the closest honest answer.

Five reasons a job stops

Row limit: your maximum rows was reached. More may exist. Credit limit: your maximum credits was reached. More may exist. User pause or cancel: you stopped it. Source failure: the provider stopped responding or returned an error, and the job was ended rather than retried forever. Cursor exhausted: the source reported no further page.

Only the last one says something about the source. Even then, it means the source had no further page at that time, not that every comment ever posted has been captured. Comments can be added, removed or restored after your export.

A worked example

Suppose a report says 180 main comments, 20 replies, 3 duplicates removed, 2 pending reply threads, and a stop reason of row_limit. Read it in order. Your 200-row ceiling was reached. Of those 200 rows, 180 are comments and 20 are replies. Three records appeared twice and were kept once. Two comments had reply threads that were opened but not finished when the limit hit.

What it does not say is that only 20 replies exist. If replies matter, raise the row ceiling or run a second job. What it also does not say is that the video has 200 comments. The reported total is still shown on the video sheet, and it remains a platform number.

Why the viewer and the export can differ too

The comment viewer loads pages while you read. An export runs a job with its own limits. If you loaded three pages in the viewer and then exported with a 200-row limit that was reached on the second page, the two will not match, and neither is wrong. Each describes its own scope. Comments can also change between the two requests.

How to write about the numbers

If you present exported data to someone else, say what the numbers are. 'Retrieved 180 main comments and 20 replies on 18 September, stopped at a 200-row limit; the platform reported 1,000 total' is a sentence that survives scrutiny. 'All 1,000 comments' is not. GlimTok gives you the pieces to say the first thing, and never claims the second.

Posts and reposts follow the same logic

The same three counts apply to a profile's posts and reposts. The profile reports a video count. The Posts tab shows the pages you loaded. The note under the list tells you whether the source ran out or you stopped. Repost tabs add one more caveat: a source may return a repost without a timestamp, and a missing time is shown as unknown rather than borrowed from the original video.

When you compare a profile's reported video count with the tiles you have loaded, remember that private, removed and region-limited videos are counted by the platform and invisible to a public source. The gap is expected, and it is not a fault in the profile or the tool.