TikTok Video URL & ID Parser — Extract IDs & Embed Links | FaasTools
Extract the video ID and username from any TikTok link, then generate a canonical video URL, embed URL, and oEmbed endpoint. Works offline in your browser.
Paste a TikTok link or video ID
Works with full video links, short links, profile URLs, and raw numeric IDs.
Supported link formats
| Input | What the parser returns |
|---|---|
| tiktok.com/@user/video/123… | Video ID, username, canonical URL, embed URL, and oEmbed endpoint. |
| 1234567890123456789 | Video ID, embed URL, and an oEmbed endpoint built from the ID. |
| @username | Normalized username and a direct profile URL. |
| vm.tiktok.com/… | Short-link detection with guidance for getting the full URL. |
The parser works entirely offline. It does not download videos or bypass privacy settings.
TikTok Video URL & ID Parser — Extract IDs & Embed Links | FaasTools
Extract the video ID and username from any TikTok link, then generate a canonical video URL, embed URL, and oEmbed endpoint. Works offline in your browser.
How it works
-
Paste a TikTok link or ID
Paste a full TikTok video link, a short vm.tiktok.com link, a profile URL, a raw numeric video ID, or an @username. The parser accepts the common formats you meet in practice.
-
Run the parser
Press parse or hit Enter. The tool reads the input locally, identifies the video ID and username where available, and shows a short-link notice if the URL still needs expanding.
-
Copy the ID, username, or URLs
Each field has its own copy button: the numeric video ID, the username, the canonical video URL, the embed URL, and a ready-made oEmbed endpoint. Copy only the value you need.
-
Use the links in your embed or report
Use the canonical URL for citations and reports, the embed URL for iframes, and the oEmbed endpoint for server-side metadata requests. The parser does not fetch or download the video.
Benefits
Clean IDs from messy links
TikTok links often arrive with tracking parameters, mobile paths, or a short redirect. The parser isolates the numeric video ID and username so you can reuse them without manual string editing.
Canonical, embed, and oEmbed URLs
One input produces the three URLs developers and creators usually need, which removes the guesswork of assembling TikTok paths by hand and reduces broken embeds.
Handles short links and raw IDs
Short links and raw IDs are detected explicitly. When a link cannot be expanded locally, the tool says so and explains how to copy the full URL from the browser instead of returning a wrong ID.
No API key or account
The tool is pure client-side text parsing. It does not call TikTok, does not require an API key, and does not need any account or permission.
Works offline and on mobile
Because nothing is sent to a server, the parser works offline once the page is loaded, and the layout is usable on a phone when you need a quick ID lookup.
Frequently Asked Questions
It extracts the numeric video ID and the username when they are present, then builds a canonical video URL, an embed URL, and an oEmbed endpoint, each with a copy button.
It detects short links and shows a warning, but it cannot follow the redirect without a network request. Open the short link once in a browser and copy the full URL from the address bar, then parse that.
No. The parser only processes text and builds URLs. It does not fetch video files, remove watermarks, or bypass private or age-restricted content.
The canonical URL is the public video page, suitable for citations and sharing. The embed URL points to TikTok's embeddable player, suitable for an iframe on a website.
It is the endpoint TikTok exposes for retrieving embed metadata such as title, author, and thumbnail. The parser builds the URL with your video link encoded, and you call it from your own server.
Yes. Paste a numeric ID with 8 to 25 digits and the parser returns the ID, an embed URL, and an oEmbed endpoint. Username-based URLs cannot be rebuilt without the username.
It means the link is a redirect such as vm.tiktok.com or /t/. The numeric ID is not inside the short link, so the safe path is to expand it once in a browser before parsing.
Yes. The parser is free, runs entirely in your browser, and sends nothing to a server. No account, API key, or installation is required.