TikTok web versus the app

MaskWright is a desktop browser on Windows 10 and 11. TikTok web is not the TikTok app. I use web for Ads Manager, Business Center, and creator ops that actually exist in a Chromium window. I use a phone I hold for the rest.

That split is the useful fact in the first screen. A mobile user agent on a desktop profile is still a desktop profile. This product has no cloud phones and no Android runtime.

What web is good for

Authorized creator accounts I already own: inbox that exists on web, analytics that exist on web, Business Center, Ads Manager. TikTok creator accounts you own. TikTok Ads Manager isolation.

Public looking that TikTok already shows a browser: a video page, a public profile, an ads library when it is public. I keep that looking in a profile with no brand login, same rule as Instagram research without mixing jars.

Multiple accounts on one PC still applies. Web cookies are still cookies. Two creator logins in one folder are one session.

What still belongs on a phone

A lot of creation, a lot of device attestation, and anything TikTok only ships in the iOS or Android app. I do not pretend a headed Chromium window is a phone.

Mobile antidetect is not a desktop profile. Cloud phones versus local Windows is the custody warning: a rented phone is someone else's device with your login.

TikTok device checks we can see is the honesty note. I will not write a bypass. If TikTok asked for the app, I open the app on hardware I hold.

Do not dress the desktop as a phone

Client Hints in this product model desktop OS families. mobile: false. Pasting iPhone in the user agent while WebGL still looks like a Windows GPU is the kind of mismatch I refuse to ship as advice.

Isolation still matters on web

Each MaskWright profile gets its own user-data-dir. profiles.json is encrypted. The Chromium tree is not. No team seats. No Playwright product. Bring your own HTTP or SOCKS5 if that entity already uses an exit.

I do not load unofficial growth extensions into a TikTok work profile. Instagram scheduling without unofficial helpers is the same refusal on another network: if the vendor wants the cookie instead of an official role or API, I skip it.

2FA stays on a device I hold. I do not paste codes into a rented browser pane.

How I actually run it

Brand A web ops: one local profile, official login, Suite-equivalent on TikTok (Business Center / Ads Manager), closed when I am done.

Brand B: new empty profile. Same locale is fine. Same cookies are not.

Research: third empty profile, usually logged out.

Phone: the physical phone for that brand, if the brand has one. Not a cloud phone farm.

FAQ

Can I run TikTok only in the browser?

You can run the parts TikTok put on web. You cannot honestly replace the app for every creator workflow. Check the feature on web before you promise a client it lives in MaskWright.

Will a desktop profile pass app device checks?

I do not claim that. Device checks that want a phone want a phone. TikTok device checks we can see.

Is a cloud phone "safer" than local Windows?

Safer for whom? The vendor holds the session. Local Windows means the folder is on your disk. That is the trade I chose. It is not a trophy score.

Do I need a mobile proxy for web?

Only if you already use one for a reason that is not "look like a phone." A mobile ASN in front of a desktop browser is another mismatch. Match the exit to the job, or use no extra exit.

Use web for web. Use the app on a phone you hold. Keep each authorized login in its own local folder.

More notes sit under Social media. Download MaskWright for the Windows desktop launcher.