Read a published video report
Resolution, bitrate, codec and evidence labels each answer a different question.
5 min read · Updated November 3, 2026For interpreting the Check video result without mixing different streams.
Begin with the report identity
Record the public post link and checked-at timestamp. Counts, available renditions and public metadata can change. A report reused from the short server cache retains its original checked-at time rather than claiming a fresh observation.
Next identify the source of the summary. Browser, Embed and Mobile web do not name the same file. If one stream cannot be inspected, a successful probe of another remains separate. The source label travels with its properties.
Read the evidence level
Metadata only means the value was exposed in the source response. Media headers checked means bounded media data was inspected for supported properties. Neither label is a visual-quality score. A rendition advertised in metadata is not proof that a player actually chose it.
| Label / state | What it supports | What it does not prove |
|---|---|---|
| Metadata only | The source response reported these properties. | The file was inspected or every viewer receives it. |
| Media headers checked | Properties were read from that identified media file. | Every pixel was visually evaluated or original samples match. |
| Not verified / unavailable | This check could not establish the value. | A zero, a failed upload or a penalty. |
| Phone — TikTok app | A separate observation would be required. | Mobile web is equivalent to a native phone app. |
Interpret resolution, frame rate and size
The p label uses the shorter pixel dimension. A 576 × 1024 stream is 576p here. Read exact dimensions before comparing it with a service that groups that size under a conventional tier. Dimensions describe the raster, not how sharp the original camera shot was.
Frame rate describes timing. A reported or inspected average can be fractional, such as 29.97 or 59.94. If it is absent, do not borrow another rendition’s rate. Duration should belong to the same identified media or be presented with its metadata source.
The checker displays binary file sizes in MiB. A decimal megabyte and a mebibyte are different units. A small difference caused by units is not a new encode or missing video data.
Keep bitrate and codec in context
Reported bitrate is supplied by metadata. File-average bitrate is calculated using size and duration. The latter may include audio and container overhead, so it is not automatically a measurement of the video track’s instantaneous or target bitrate.
H.264 and HEVC describe different compression formats. Two streams with different codecs cannot be ranked reliably by bitrate alone. Inspect the same scene and keep dimensions, frame rate and source identity attached to any comparison.
Read color, post information and engagement separately
HDR/SDR status needs relevant verified color metadata. Resolution, a filename containing HDR or a vivid-looking thumbnail is not enough. Unavailable color information should remain unavailable.
Creator details, caption and the displayed sound label are public metadata. Engagement counts describe activity exposed by TikTok. The rate shown by Fulres uses likes, comments and shares divided by views, multiplied by 100 when the necessary values are known. It does not include every possible interaction or establish recommendation eligibility.
Read recommendation signals without assuming a shadowban
The recommendation check first reads TikTok’s public mobile-web indexEnabled boolean for the exact post. Source and evidence shows its raw value, field path, source URL and retrieval time. A known boolean skips all provider requests. If the direct flag is unavailable, it requests a flag from the configured provider: TikWM by default, or optionally TikTokAPI.io through a server-only integration. The source is shown with the result. For TikWM only, if the server cannot verify it, the browser makes one direct bounded POST to TikWM. Optional key-based requests never run in the browser or silently switch provider. The direct request exposes your browser IP, website origin and ordinary request headers, with credentials and referrer omitted. A known server boolean skips the browser lookup.
Possible recommendation restriction means TikTok returned a matching indexEnabled=false or the provider returned a matching true restriction flag. No indexing restriction flag means indexEnabled=true. No restriction flag returned means a provider returned false; it does not prove official eligibility, active recommendations or an unrestricted account. Not verified means neither the direct lookup nor the provider returned a recognized boolean with matching video identity. The public indexing flag is not TikTok’s official Analytics eligibility notice.
Source and evidence keeps server/browser attempts, flags or failures, retrieval times and raw public moderation fields separate. Both public codes 1 and 3 occurred on posts the user confirmed restricted, so Fulres withdrew its earlier code-3 inference. Codes, low views and a false prohibited flag do not establish For You eligibility. The source’s evaluation time and cache freshness remain unknown.
To confirm post eligibility, open the post in TikTok, then More insights / Analytics and look for an eligibility notice. Review the reason and appeal there if TikTok provides a restriction notice. A post-level provider flag does not diagnose an account-wide ban.
Use a report to answer a narrow question
A good question is: which dimensions were inspected for this Browser stream at this time? A question the report cannot answer is: did every phone viewer receive my original export unchanged? Use the former to build a repeatable comparison, and leave the latter unverified without additional evidence.
- Post link and checked-at time recorded.
- Summary source and evidence level read.
- Bitrate basis checked before comparison.
- Exact dimensions compared, not only tier names.
- Missing and native-app values left unverified.