Video Hosting for WordPress Landing Pages and Shopify Sales Pages

Vidalytics and Wistia document the most complete route onto a WordPress landing page or a Shopify sales page, because each publishes platform-specific instructions for both builders and neither depends on a URL field that only recognizes public video services. Vimeo follows because it is one of two services WordPress lists as a built-in embed provider and one of two URL sources Shopify accepts for product media. SproutVideo publishes a responsive inline embed and a Shopify walkthrough, Bunny Stream hands a developer an iframe with explicit loading control, and YouTube is the easiest to paste in and the hardest to keep the visitor inside.

This page ranks documented placement, not overall product quality. Where a claim is not in the first-party documentation we read on September 16, 2026, the page says so rather than guessing. The sales-funnel hosting guide covers the wider campaign decision, and the VSL hosting guide covers the single sales video itself.

What does a WordPress or Shopify sales page need from its host?

A store page and a landing page ask the same three things. The video has to arrive inside a builder the marketer already uses, it has to stay the destination rather than becoming a doorway to somewhere else, and it must not make the page slower than the offer can survive.

The first requirement decides more than it looks like it does. Both builders accept arbitrary embed code only in a specific place, and both restrict a simpler URL field to a short list of public services. A host that publishes an exact route into each builder saves a team from discovering that restriction after the campaign is booked.

The second requirement rules out the players that sell someone else’s inventory in the last ten seconds. The third is ordinary web performance work, and it belongs to the page as much as to the host. Our fast video hosting guide covers the architecture side of that question.

How is a hosted video placed in WordPress?

WordPress documents two routes, and the difference between them decides which hosts are easy.

The first is the Embed block. WordPress states that when you embed content “you don’t need to upload the content to your WordPress site” and that you paste the third-party URL into a generic Embed block or a service-specific one. The catch is the list: the documented services include Vimeo and YouTube but none of the other four hosts here. The same page notes that only public and unlisted YouTube videos can be embedded, not private ones.

The second is the Custom HTML block, which accepts a pasted embed code, previews the output beside the editor, and can be inserted by typing a slash command. There is a real constraint on a multi-author site. WordPress documents that from version 7.0 the CSS and JavaScript panels appear only for users holding the unfiltered_html capability, and that a user without it has the block sanitized so disallowed tags such as script and iframe are stripped when the post is saved. A contributor cannot publish a player.

Wistia documents both routes and adds a warning worth repeating: use its inline or popover embed and avoid the iframe fallback on WordPress, because the editor “tends to modify the iframe code and break expected functionality.” It also documents adding Wistia to the oEmbed provider list so a plain link works. Vidalytics documents the same pair, registering an oEmbed provider in the theme functions file and then pasting its share link into the Embed block, and states plainly that the hosted free tier of WordPress.com is not compatible because it does not allow custom embed code. Vimeo documents a responsive embed code by default with a fixed pixel option, and SproutVideo documents a responsive inline code that needs nothing installed on the receiving page.

How is a hosted video placed on a Shopify page?

Shopify separates product media from page sections, and the rules differ.

Product media has documented limits. Shopify states a maximum of 250 images, 3D models, or videos per product and a store ceiling of 1,000 video uploads per week. An uploaded file may be MP4, MOV, or WebM, up to 1 GB and up to ten minutes, and Shopify converts and serves it as MP4 or HLS. Adding a video by URL is narrower still: the documentation gives the standard YouTube watch format and the direct Vimeo format, says that Shorts links are not currently supported, and states that “URLs other than YouTube or Vimeo URLs aren’t supported.”

Everything else arrives through the theme. Shopify documents a Custom Liquid section as the place to put third-party code “instead of editing your theme code directly,” alongside app blocks, app embeds, and the code editor for merchants comfortable with Liquid, HTML, and CSS.

Wistia states the consequence bluntly: “Shopify’s Video section does not support Wistia URLs at this time, so Custom Liquid/Custom HTML is the best alternative,” and it documents wrapping the embed in a div with a max-width so the responsive player stops growing. SproutVideo documents opening the page in the Shopify admin, clicking the Show HTML control in the rich text editor, and pasting its inline embed. Vidalytics documents pasting its embed code into the video element’s settings and adds the honest caveat that a homepage placement works only “if you’re using a sectioned theme and if it accepts Custom HTML/third-party embed codes.” It separately documents a storefront connection that reads a Shopify domain and a Storefront access token to put product overlays inside the player, available on its Pro plans and above. For Bunny Stream we found no Shopify-specific article in the documentation we checked, which leaves the generic iframe and the theme editor.

Which hosts fit these two builders best?

The table reports only what the linked first-party documentation states on the date given.

Prices come from the verified review tables; confirm current terms with the vendor before buying. The Vidalytics review, Wistia review, and SproutVideo review carry the dates those figures were checked.

Why do the built-in options fall short on a selling page?

Three shortcuts are always available and each costs something specific.

YouTube is the cheapest and the leakiest. Its player documentation states that since September 25, 2018 a rel value of 0 makes related videos come from the same channel rather than removing them, and that “you will not be able to disable related videos.” End screens compound it: YouTube documents them in the last five to twenty seconds of a video, linking to other videos, playlists, channels, and, for partner-program members, an external site. The same parameter reference warns that enabling autoplay means playback data collection and sharing occur on page load. The YouTube review covers where that trade is still worth making.

Shopify hosted video is fine for a short product clip and wrong for a long argument. The ten-minute ceiling ends the discussion for most sales videos, and Shopify documents no engagement timeline, no timed action, and no lead capture around its own player.

The WordPress media library is the option teams reach for without thinking. Its Video block documents upload, poster image, caption tracks in WebVTT, inline playback, and three preload settings, and the documentation itself cautions that the Auto setting “makes the biggest impact on your page or post’s load speed, especially with larger video files.” What it documents nowhere is adaptive delivery, viewer reporting, or anything that happens when the viewer stops watching.

How do you keep the video from slowing the page?

Reserve the space first. Bunny Stream’s embed example ships with an aspect-ratio style and a loading attribute set to lazy, along with an allow attribute covering autoplay, encrypted media, picture in picture, and fullscreen; it also documents a padding-based wrapper for older browsers and a preload parameter that starts downloading before playback is requested.

Then choose the embed type deliberately. Wistia documents a script-based inline embed it calls faster to become ready than its iframe fallback, which loads the player on a separate page first. SproutVideo documents that its responsive option needs nothing installed or configured on the receiving page. Vimeo’s default embed is responsive already, with a fixed size available when a layout demands it.

After that the work is the page’s. A single hero player treated carefully beats three below-the-fold embeds that all initialize at once, and a consent tool or theme script is often the real cost. Measure the published page on representative phones, not an empty preview.

What should be tested before the page goes live?

• Confirm the embed survives a save in the actual editor, since WordPress can rewrite pasted iframe markup and a Shopify theme may not accept third-party code at all.
• Check the block or section under a non-administrator account if other people publish on the site.
• Load the page on a phone and confirm the player fills its container without pushing the offer below the fold.
• Verify the muted start, the click-to-play state, and the blocked-autoplay state, using our muted autoplay guide as the checklist.
• Confirm captions, keyboard focus, volume, seeking, and fullscreen still work inside the builder’s markup.
• Watch the last thirty seconds of playback and see what the player offers next.
• Re-measure with the consent banner, analytics, theme scripts, and checkout code present.
• Check the video is still reachable after a theme update or a page-builder version change.

Choose the host by the route it documents into the builder you already own, then design the page so a blocked player still sells. A video that a contributor cannot publish, a theme will not accept, or a browser will not start is not a hosting decision that has been made yet.