webkoding
tuberail.webkodingtheme.comLive
A YouTube gallery rendered on the site in the grid layout, with titles, view counts and durations pulled from the channel.Open the live demo →

No signup. Try it with a test card; the demo resets itself regularly.

An embed plugin gives you a video on a page. Tuberail can go further and mirror a channel or playlist into a WordPress post type on a schedule, so each video becomes a real page with its own URL, comments, categories and theme rendering.

It also takes the YouTube API quota seriously, because that is what breaks these plugins in practice. A naive gallery calls the API on every page view and stops working by lunchtime; every response here is cached against your own key.

What you get, before you pay

Everything in the box, so there is nothing to discover after checkout.

Files

  • tuberail.zip, installed from the WordPress admin
  • Unminified source, no obfuscation
  • Changelog and sample data

Licence

  • 1 WordPress site
  • Licence key sent by email after payment
  • GPL v2 or later

Updates and support

  • 1 year of updates and email support
  • After that the software keeps working
  • Renew only if you want new versions

Requirements

  • WordPress 6.0+
  • PHP 7.4+
  • YouTube Data API v3
  1. 1
    Add your API key

    Your own YouTube Data API v3 key. Every response is cached against it.

  2. 2
    Point a gallery at a channel

    A channel ID, an @handle, a playlist, or several channels in tabs.

  3. 3
    Publish, or import

    Show a grid, masonry, carousel or list — or mirror the channel into real WordPress posts.

What it does

  • Four layouts — grid, masonry, carousel and list, responsive at every width
  • Point a gallery at a channel ID, an @handle, a playlist, or several channels in tabs
  • Auto-import videos into a WordPress post type on a schedule
  • schema.org VideoObject and ItemList structured data, with a noindex toggle
  • Facade embeds — the player loads on click, so Core Web Vitals stay green
  • Channel stats card, subscribe button, and a WP-CLI import command

What you need

  • WordPress 6.0 or newer, PHP 7.4 or newer
  • A YouTube Data API v3 key of your own, from the Google Cloud console
  • The channel ID, @handle or playlist you want to show
  • WP-Cron running, if you want videos imported into a post type on a schedule

Runs on your own WordPress with your own YouTube Data API key — free from Google, and quota-limited by them rather than by us.

What Tuberail does not do

  • It does not host or upload video. Playback is YouTube's; this is how the videos reach your site.
  • It does not come with an API key, and the quota is Google's rather than ours. An unrestricted key that leaks is your bill.
  • It cannot show private or unlisted videos the API will not return.
  • Imported posts are copies of metadata, not of the video. Delete a video on YouTube and the post remains until the next import.

Questions

Why do I need my own API key?

Because YouTube quota is per key, and a shared key would mean your gallery stops working when somebody else’s site has a busy day. Yours is free to obtain from the Google Cloud console.

Will it burn through my quota?

No — that is the failure mode this was built around. A naive gallery calls the API on every page view and stops working by lunchtime; here every response is cached, so page views cost nothing.

What does importing videos into posts actually do?

It mirrors a channel or playlist into a WordPress post type on a schedule, so each video becomes a real page with its own URL, comments, categories and your theme’s rendering — pages you own, rather than embeds you rent.

Will embedded video wreck my Core Web Vitals?

Not with facade embeds turned on: a thumbnail is shown and the player only loads when somebody clicks. A page of ordinary YouTube iframes is one of the most expensive things a site can serve.

Does it output structured data?

VideoObject and ItemList, with a noindex toggle for when the imported pages should not compete with your own content.

Everything else is in the Tuberail documentation, and anything it does not answer goes to support@webkoding.com.

Not quite it? Three nearby

Not ready to buy?

We will write when there is a new plugin, or a release worth knowing about. A few emails a year, each about something we actually shipped — no offers, no sequence, and your address goes nowhere else.

One click to leave, from any of them. What we do with it.