Videokr vs a WordPress player plugin (FluentPlayer)

FluentPlayer and similar WordPress player plugins give you a good player inside WordPress for media you host yourself — your server or bucket serves every byte, and analytics cover that one site. Videokr hosts and delivers the video, works on any site through an iframe or script embed, reports across all of them in one dashboard, and still gives WordPress a free plugin with a shortcode, block and Insights screen.

Updated 2026-08-18 · Markdown version

The structural difference

A WordPress player plugin is code that runs in your site and plays files you provide. That means:

• Delivery is yours. Your host or your bucket serves the bytes, and a popular page is your bandwidth problem.
• Reach is one platform. The player exists where WordPress exists. A landing page on Webflow or a Shopify product page cannot use it.
• Analytics are per site. Whatever the plugin records, it records inside that installation.
• Updates and conflicts are yours. A player is JavaScript inside your theme, alongsize everything else.

A hosted platform inverts all four: the file lives on delivery infrastructure, the embed is plain HTML that works anywhere, and the analytics are central.

What Videokr does for a WordPress site

The free plugin — on every plan, including free — adds:

• [videokr id="vid_abc123"] shortcode with width, ratio, autoplay, muted and start attributes.
• A Gutenberg block with a visual picker over your library, thumbnails included.
• An Insights screen: plays this month against your allowance, all-time totals, a 30-day chart, most-played videos and recent leads.
• API-key connection, revocable from Videokr, one key per site.

WordPress stores one shortcode. No media in the library, no video bytes through your host, no backup bloat.

Where a plugin is the better answer

Say it plainly:

• You want no external service in the stack, for policy or preference.
• You already pay for a CDN and bucket and are happy operating them.
• One-time site-licence pricing suits you better than any subscription, and you never need the video off WordPress.
• You need the player deeply hooked into WordPress internals — the plugin's own forms, CRM or membership integrations inside the same install.

Where hosting wins

• The same video on WordPress, a Webflow landing page and a client's Shopify store, measured in one place.
• No bandwidth risk when a page does well.
• One retention curve per video across every site it appears on.
• Access control that survives a copied embed code: domain-locked embeds.

Running both

Perfectly reasonable: keep the plugin's player for incidental clips inside posts, and host the videos that carry commercial weight — the demo, the pricing-page explainer, the course lessons — on Videokr with CTAs and retention tracking.

How to read this page

Videokr's own numbers here are exact. Everything about the other product is limited to how it is structured — what it hosts, where it plays, what it prices on — because feature lists and prices change without notice and we will not print a number for someone else's product that might be stale by the time you read it. Check their current pricing page before you decide, and try both free tiers: that is a better comparison than any table written by a vendor.