Paste the video URL into its own line in the block editor and WordPress turns it into a playable embed automatically. WordPress can auto-embed links from YouTube and Vimeo natively, and TikTok links in many cases too. If the automatic embed doesn't appear, the fix is almost always a wrong URL format or a caching issue, both covered below.
This works the same way on any Flashcloud WordPress install, since embeds are HTML your existing cache stack serves like any other content.
The block editor method (use this first)
In the post or page editor:
- Click into an empty paragraph, or add a new block with
+. - Paste the full video URL, for example
https://www.youtube.com/watch?v=VIDEO_ID,https://vimeo.com/VIDEO_ID, orhttps://www.tiktok.com/@user/video/VIDEO_ID. - Press Enter. The URL converts into an embed block with a live preview in the editor.
If it doesn't convert, you can force it: add a block, search for "YouTube," "Vimeo," or "TikTok" specifically, and paste the URL into that block's URL field instead of a generic paragraph. The dedicated blocks are more reliable than auto-detection because they skip the guesswork.
Common reasons the auto-embed fails
- Shortened or parameter-heavy URLs. A link like
youtu.be/VIDEO_ID?si=xxxxxusually still works, but if it doesn't, copy the canonicalwatch?v=link from the video's Share button instead. - Private or unlisted content restrictions. TikTok in particular can block embedding for certain accounts or videos. If the block editor preview stays blank, the video's owner has likely disabled embedding.
- Pasting inside another block. If you paste the URL into existing text mid-sentence, WordPress won't auto-embed it. It needs to be alone on its own line in its own block.
Why the embed sometimes doesn't show on the live page
If the video previews fine in the editor but not on the published page, the usual cause is caching, not a broken embed. Every Flashcloud WordPress install runs LiteSpeed Cache with full-page caching, so a newly added embed won't show until the cache is purged.
Ad blockers and privacy extensions can also hide YouTube and TikTok embeds in your own browser during testing. Check the page from an incognito window or ask someone else to confirm before assuming the embed is broken.
When to use a plugin instead
The native block editor covers a single embedded video on a page. Reach for a dedicated plugin only when you need more than that:
- Video galleries or playlists that pull multiple videos from a channel automatically.
- Lazy-loading beyond what your theme provides, so the video's JavaScript and thumbnail don't load until a visitor scrolls to it. This matters more on pages with several embeds, since each one can add its own render-blocking script.
- Custom players that strip branding, autoplay muted, or loop a background-style video.
If you're already fighting page speed with a plugin-heavy install, work through My WordPress site is slow first. Multiple video embeds are exactly the kind of "heavy plugin plus heavy content" combination that article flags, and a video gallery plugin on top of an already bloated theme will compound the problem rather than fix it.
Don't upload video files directly to WordPress
It's technically possible to upload an .mp4 to the Media Library and embed it with the native Video block, but avoid this for anything longer than a few seconds. Self-hosted video eats your disk space, doesn't get the adaptive bitrate streaming YouTube and Vimeo provide, and every visitor downloads the full file from your server instead of a video CDN built for it. Upload to YouTube or Vimeo (unlisted if you don't want it public) and embed the link instead.
Test before you rely on it
Because embeds depend on how a caching layer and a third-party player interact, treat a new video embed like any other risky change: try it on a copy of the page first if it's going on a high-traffic page or a storefront. See Using WordPress staging for the workflow. This is especially worth doing if you're adding video to a product page on a WooCommerce store, where you don't want to discover a caching conflict after the page is already live.
If you've confirmed the URL is correct and purged cache and the embed still won't render, open a ticket from the portal so we can look at what's happening on the server side.