Reach, engagement and your file: what each result means
Understand public statistics, account eligibility and temporary file handling as separate questions.
4 min read · Updated November 3, 2026For interpreting reach claims and understanding what happens to selected files.
Start with what public numbers actually say
Views, likes, comments, shares and favorites are activity counts when TikTok exposes them. They can be incomplete or change with time. A missing field is not a count of zero, and a new check may not return the same public metadata as an earlier one.
Low views do not identify a cause. They do not establish a hidden penalty, prove an export was compressed, or show that a particular metadata edit changed recommendation eligibility. Those claims need different evidence.
Understand the engagement calculation
Fulres uses likes plus comments plus shares, divided by views, multiplied by 100 when the necessary counts are available. Favorites and the Downloads statistic are shown separately; they are not quietly added to this formula.
For an illustrative post with 1,000 views, 70 likes, 10 comments and 20 shares, the displayed calculation would be (70 + 10 + 20) ÷ 1,000 × 100 = 10%. These invented values explain the formula; they are not a benchmark or a result for your account.
| Situation | Interpretation |
|---|---|
| All required counts known and views positive | Calculate the stated rate using those values. |
| A required interaction count missing | Do not replace it with zero to manufacture a rate. |
| Views unavailable or zero | Do not divide by an unknown or zero value. |
| Download count displayed | A public TikTok statistic, not a Fulres download action. |
Use account-specific information for eligibility
TikTok provides notices and analytics within its own account interfaces. Check those for an actual eligibility message, restriction or appeal option. A public-link checker does not have equivalent access to your account’s internal eligibility state.
If a post has an explicit notice, read that notice rather than replacing it with a theory about resolution or codec. If no notice is available, the reason for low reach remains uncertain. Fulres should not invent an explanation from engagement ratios.
The checker first reads the matching post’s public mobile-web indexEnabled boolean. False is a possible restriction signal; true is not proof of For You eligibility. Both retain their source and retrieval time and skip provider calls. When that direct flag is unavailable, the checker uses TikWM by default, requesting a flag from the server and, only if no verified flag is available, directly from your browser. An operator can instead configure TikTokAPI.io as a server-only provider; that path never contacts a provider directly from your browser. The direct request exposes browser IP, origin and ordinary request headers, with credentials and referrer omitted. A matching provider flag is a third-party report. Public moderation codes 1 and 3 are raw observations only; they do not diagnose eligibility, an account-wide ban or active recommendations. Source and evidence retains both attempt outcomes and times.
Follow the file through Fulres
When you select a file for optimization, the browser sends it to the processing backend. The native processing flow uses temporary files and verifies its prepared output. This is different from a tool that processes every byte only in the browser.
Normal completion, failure and cancellation paths clean up processing files. Unexpected termination can leave temporary artifacts; the implementation does not justify promising that no orphan can ever exist. A prepared video is not automatically posted to TikTok.
- 01Select file
- 02Temporary backend preparation
- 03Verified result in current tab
- 04Explicit send to TikTok
Distinguish history, checking and posting
History stores export details such as dimensions, filename and date. It is not a recoverable library of your video bytes. The checker reads public metadata and bounded media ranges and does not save a video library for later download.
A real TikTok transfer requires the connected account, posting permission and explicit confirmation. The local Demo preview shows sample controls and never creates that permission. Closing or reloading the tab can discard active media even though a metadata record remains.
Keep a useful record without exposing secrets
For troubleshooting, retain the original file locally and record the post link, report time, evidence labels and error text. Do not share access tokens or signed transfer URLs as part of an ordinary quality comparison.
Consult the site’s Privacy Policy and account controls for stored-account data. This guide explains the current processing workflow; it is not a substitute for account-specific notices from TikTok or a guarantee about every infrastructure provider’s retention.
- Public counts are interpreted as counts, not a reach diagnosis.
- The engagement formula and any missing inputs are visible.
- Original media is retained outside export history.
- A preparation result is kept separate from posting authorization.