TikTok Short Links Supported
Supports vt.tiktok.com, vm.tiktok.com, and regular tiktok.com video links.
A download page for TikTok share links, supporting vt.tiktok.com, vm.tiktok.com, and standard video URLs. After parsing a public video, it returns downloadable video assets and uses a download proxy for CDN requests when needed.
Supports vt.tiktok.com, vm.tiktok.com, and regular tiktok.com video links.
When parsing public pages, temporary access state is handled automatically. Manually maintained login cookies are not the default path.
Some TikTok video URLs validate the request source. The download button prioritizes an on-site download URL to reduce direct-link failures.
Supports vt.tiktok.com and vm.tiktok.com links shared from the app, as well as tiktok.com/@user/video/id from the browser address bar.
The tool reads public page information and returns the title, author, cover, and video download items.
TikTok direct links sometimes validate the request source. Use the download button to save the file instead of copying the CDN URL manually.
When public TikTok videos appear in operations or editing work, save them to a local material library first, then transcode or compress them in batches.
TikTok share short links often include region, language, or redirect parameters. The page resolves the final video address first, then returns download items.
After downloading, you can keep using VideoKit to convert MP4 or WebM, compress file size, trim clips, or extract audio.
Many TikTok video direct links fail outside their original request context, so this page emphasizes saving through the download button instead of showing only raw links.
The first version does not make manual cookies, account login, or regularly refreshed tokens a maintenance requirement. Public links return download items when they can be parsed.
If a video is only visible in certain regions, age-restricted, deleted, or non-public, the page may not find downloadable assets.
Some TikTok video URLs validate the request source and temporary session, so opening them directly may fail. The download button uses the same lightweight backend entry.
No. The first version only uses automatically obtained temporary public sessions.
No. It currently only handles publicly accessible share links.