Dropndot Solutions

<p>Dropndot Video Library is a powerful WordPress plugin that transforms your website into a comprehensive video management platform. Create, organize, and display videos from popular platforms like YouTube, Vimeo, Dailymotion, Facebook, TikTok, and more through an intuitive custom post type interface.</p>
<h3>Key Features</h3>
<ul>
<li><strong>Multi-Platform Support</strong>: Embed videos from YouTube, Vimeo, Dailymotion, Facebook, TikTok, and other video platforms</li>
<li><strong>Custom Post Type</strong>: Dedicated “Videos” post type with full WordPress integration</li>
<li><strong>Taxonomies</strong>: Organize videos with categories and tags</li>
<li><strong>REST API Support</strong>: Full REST API integration for headless implementations</li>
<li><strong>WPGraphQL Support</strong>: GraphQL API support for modern applications</li>
<li><strong>Custom Templates</strong>: Includes archive, single, and taxonomy templates</li>
<li><strong>Admin Interface</strong>: User-friendly video management interface</li>
<li><strong>Settings Page</strong>: Customize URL slugs for videos and archives</li>
<li><strong>Thumbnail Support</strong>: Featured image support for video thumbnails</li>
<li><strong>SEO Friendly</strong>: Proper meta descriptions and structured data support</li>
</ul>
<h3>Supported Video Platforms</h3>
<ul>
<li>YouTube</li>
<li>Vimeo</li>
<li>Dailymotion</li>
<li>Facebook</li>
<li>TikTok</li>
<li>And many more through embed URLs</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to third-party video platform APIs to retrieve oEmbed/metadata so it can normalize URLs, generate embed links, and build thumbnails for videos saved in the Video post type.</p>
<h4>Vimeo API</h4>
<p>Used to fetch metadata and thumbnails for Vimeo URLs.<br />
Data sent: the video ID parsed from the URL.<br />
When sent: when a Vimeo URL is saved or processed.<br />
Terms: https://vimeo.com/terms<br />
Privacy policy: https://vimeo.com/privacy</p>
<h4>Facebook Graph oEmbed API</h4>
<p>Used to fetch oEmbed information for Facebook video URLs.<br />
Data sent: the original Facebook video URL and a site-configured access token (if provided via filter).<br />
When sent: when a Facebook video URL is saved or processed.<br />
If the oEmbed response does not provide a thumbnail URL, the plugin also fetches the original Facebook video page HTML and extracts the <code>og:image</code> meta tag to determine a thumbnail.<br />
Terms: https://www.facebook.com/legal/terms<br />
Privacy policy: https://www.facebook.com/privacy/policy/</p>
<h4>TikTok oEmbed API</h4>
<p>Used to fetch oEmbed information for TikTok video URLs.<br />
Data sent: the original TikTok video URL (when available/stored in post meta for normalization).<br />
When sent: when a TikTok URL is saved or processed.<br />
Fallbacks: if needed, the plugin fetches HTML from <code>https://www.tiktok.com/embed/{video_id}</code> and also tries <code>https://www.tiktok.com/v/{video_id}</code> to parse <code>og:image</code> and JSON-LD for a thumbnail.<br />
Terms: https://www.tiktok.com/legal/terms-of-service<br />
Privacy policy: https://www.tiktok.com/legal/privacy-policy</p>
<h4>Wistia API</h4>
<p>Used to fetch metadata for Wistia media URLs.<br />
Data sent: the Wistia media ID parsed from the URL.<br />
When sent: when a Wistia URL is saved or processed.<br />
Terms: https://wistia.com/terms<br />
Privacy policy: https://wistia.com/privacy</p>
<h4>Twitch Helix API</h4>
<p>Used to resolve Twitch stream/channel details for embed generation.<br />
Data sent: Twitch channel username (passed as <code>user_login</code>) to resolve live-stream thumbnails; the request includes a <code>Client-ID</code> header obtained via the filter <code>DROPNDOT_VIDEO_LIBRARY_twitch_client_id</code>.<br />
When sent: when a Twitch URL is saved or processed.<br />
Terms: https://www.twitch.tv/p/en/legal/terms-of-service/<br />
Privacy policy: https://www.twitch.tv/p/en/legal/privacy-notice/</p>
<h4>Veed oEmbed API</h4>
<p>Used to fetch oEmbed information for VEED links.<br />
Data sent: the original VEED video URL.<br />
When sent: when a VEED URL is saved or processed.<br />
Terms: https://www.veed.io/terms<br />
Privacy policy: https://www.veed.io/privacy</p>
<h4>Loom oEmbed API</h4>
<p>Used to fetch oEmbed information for Loom links.<br />
Data sent: the original Loom video URL.<br />
When sent: when a Loom URL is saved or processed.<br />
Terms: https://www.loom.com/terms<br />
Privacy policy: https://www.loom.com/privacy-policy</p>
<h4>Rumble Video Page Fetch</h4>
<p>Used to fetch the Rumble video page HTML to extract thumbnail metadata (Open Graph <code>og:image</code>).<br />
Data sent: the Rumble video page URL built from the video ID parsed from the embed URL.<br />
When sent: when generating fallback thumbnails for Rumble embed URLs (and when processing URLs where no provider API response is available).<br />
Terms: https://rumble.com/s/terms<br />
Privacy policy: https://rumble.com/s/privacy</p>
<h4>Streamable API</h4>
<p>Used to fetch metadata for Streamable URLs.<br />
Data sent: the Streamable video ID parsed from the URL.<br />
When sent: when a Streamable URL is saved or processed.<br />
Terms: https://streamable.com/terms<br />
Privacy policy: https://streamable.com/privacy</p>
<h4>Instagram oEmbed API</h4>
<p>Used to fetch oEmbed information for Instagram video URLs.<br />
Data sent: the original Instagram video URL.<br />
When sent: when an Instagram URL is saved or processed.<br />
Terms: https://help.instagram.com/581066165581870<br />
Privacy policy: https://privacycenter.instagram.com/policy</p>
<h4>Direct URL fetch for metadata parsing</h4>
<p>In some providers, the plugin requests the original video page URL to extract metadata when no provider API response is available.<br />
Data sent: a standard HTTP request to the video URL provided by the site editor.<br />
When sent: when processing supported non-API/fallback URL patterns.</p>
<h3>Support</h3>
<p>For support, bug reports, or feature requests, please visit:<br />
https://dropndot.com/support/</p>
<h3>Contributing</h3>
<p>We welcome contributions! Please see our GitHub repository for contribution guidelines.</p>
<h3>License</h3>
<p>Dropndot Video Library is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.</p>
<p>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.</p>
<p>You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/gpl-2.0.html.</p>


Dropndot Video Library

Multi-platform video embeds as a custom post type with REST API and WPGraphQL support for WordPress.

Jason Bahl

<p>WPGraphQL for Advanced Custom Fields is a free, open-source WordPress plugin that adds ACF Fields and Field Groups to the WPGraphQL Schema.</p>
<h4>Create ACF Field Groups</h4>
<p>Create ACF Field Groups and Fields using the ACF User Interface, register them with PHP, or leverage ACF local JSON. Each field group and the fields within it can be configured to “Show in GraphQL.”</p>
<h4>Query your fields with GraphQL</h4>
<p>Once your field groups and fields are configured to “Show in GraphQL,” they become available in the GraphQL Schema for querying.</p>
<h4>Supported Field Types</h4>
<p>WPGraphQL for ACF provides support for most built-in field types of ACF (free & PRO) and extends support to most field types from ACF Extended (free & PRO).</p>
<h3>Updating</h3>
<p>If you are updating from WPGraphQL for ACF v0.6.* or older, check out the <a href="https://acf.wpgraphql.com/upgrade-guide" rel="nofollow ugc">Upgrade Guide</a></p>
<p>For non-major version updates, automatic updates usually should work smoothly, but we still recommend you back up your site and test on a staging site.</p>
<p>Before updating WPGraphQL for ACF, review the release notes on <a href="https://github.com/wp-graphql/wpgraphql-acf/releases" rel="nofollow ugc">GitHub</a>.</p>
<p>We follow Semantic Versioning (Semver) for meaningful releases:</p>
<ul>
<li><em>MAJOR</em> version for incompatible API changes,</li>
<li><em>MINOR</em> version for backwards-compatible functionality additions,</li>
<li><em>PATCH</em> version for backwards-compatible bug fixes.</li>
</ul>
<p>Learn more about Semver at <a href="https://semver.org" rel="nofollow ugc">semver.org</a>.</p>
<h3>Support</h3>
<ul>
<li><a href="https://github.com/wp-graphql/wp-graphql/discussions" rel="nofollow ugc">General Help Requests</a>: For general questions and help requests, create a new topic in Github Discussions</li>
<li><a href="https://www.wpgraphql.com/discord" rel="nofollow ugc">Discord Community</a>: The WPGraphQL Discord is a great place to communicate in real-time. Ask questions, discuss features, get to know other folks using WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=bug_report.yml" rel="nofollow ugc">Bug Reports</a>: Report a bug in WPGraphQL</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/issues/new?assignees=&labels=&projects=&template=feature_request.yml" rel="nofollow ugc">Feature Requests</a>: Suggest an idea, feature, or enhancement for WPGraphQL.</li>
<li><a href="https://github.com/wp-graphql/wp-graphql/security/advisories/new" rel="nofollow ugc">Report a Security Vulnerability</a>: Report a security vulnerability.</li>
</ul>
<h3>FAQs</h3>
<p><strong>Does this work with ACF Extended?</strong></p>
<p>Yes! WPGraphQL for ACF allows you to query for (most) fields created with ACF Extended.</p>
<p><strong>Can I filter and sort queries by ACF Fields using WPGraphQL for ACF?</strong></p>
<p>At this time WPGraphQL for ACF does not support filtering or sorting queries by ACF Fields. “Meta Queries” are often very expensive to execute, so we currently do not support filtering by ACF fields out of the box, but are exploring options for supporting it without the performance penalty.</p>
<p><strong>I think I found a bug, where do I report it?</strong></p>
<p>If you think you found a bug, please open an issue on <a href="https://github.com/wp-graphql/wpgraphql-acf" rel="nofollow ugc">GitHub</a>. The more details you provide in the issue, and the more clear your steps to reproduce are, the higher chances we will be able to help.</p>
<p><strong>Can I use ACF Free or Pro with WPGraphQL for ACF?</strong></p>
<p>Yes! WPGraphQL for ACF works great with ACF Free and Pro. The Pro version of ACF has some additional features, such as Flexible Content Fields, Repeater Fields and Options Pages that are supported by WPGraphQL for ACF.</p>
<p><strong>Do I have to use Faust.js to use WPGraphQL for ACF?</strong></p>
<p>No! While <a href="https://www.wpgraphql.com" rel="nofollow ugc">wpgraphql.com</a> and <a href="https://acf.wpgraphql.com" rel="nofollow ugc">acf.wpgraphql.com</a> are built using <a href="https://faustjs.org/" rel="nofollow ugc">Faust.js</a> and Next.js, you can use WPGraphQL for ACF with any GraphQL client, including Apollo, Relay, Urql, etc.</p>
<p><strong>I have an ACF Extension that adds a new field type, will it work with WPGraphQL for ACF?</strong></p>
<p>WPGraphQL for ACF supports the field types that come with ACF (Free and PRO) as well as the field types in ACF Extended (Free and PRO). Support for additional field types can be added by using the “register_graphql_acf_field_type” API.</p>
<p><strong>Do I need WPGraphQL and ACF to be active to use this?</strong></p>
<p>This plugin is a “bridge” plugin that brings functionality of ACF to WPGraphQL. Both WPGraphQL and ACF need to be installed and active in your WordPress installation for this plugin to work.</p>
<p><strong>How much does WPGraphQL for ACF cost?</strong></p>
<p>WPGraphQL for ACF is a FREE open-source plugin. The development is sponsored by <a href="https://wpengine.com/atlas" rel="nofollow ugc">WP Engine Atlas</a>.</p>
<p><strong>Does WPGraphQL for ACF support GraphQL Mutations?</strong></p>
<p>GraphQL Mutations are not yet supported. We are working on adding support for Mutations in the future. We are waiting for the GraphQL “@oneOf” directive to be merged into the GraphQL spec before we add support for Mutations.</p>
<p><strong>Does this work with Field Groups registered in PHP or JSON?</strong></p>
<p>Yes! You can register ACF Field Groups and Fields using the Admin UI, PHP or JSON. WPGraphQL for ACF will detect the Field Groups and Fields and add them to the GraphQL Schema. If using PHP or JSON, you will need to set the “show_in_graphql” setting to “true” to expose the Field Group and Fields to the GraphQL Schema. There might be other settings that need attention at the field group or field level that might impact the schema or field resolution.</p>
<h3>Privacy Policy</h3>
<p>WPGraphQL for Advanced Custom Fields uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect telemetry data upon user confirmation, helping us troubleshoot problems and improve the product.</p>
<p>The Appsero SDK <strong>doesn’t collect data by default</strong> and only starts gathering basic telemetry data when a user allows it via the admin notice. No data is collected without user consent.</p>
<p>When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below).</p>
<p>Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses data</a>.</p>


WPGraphQL for ACF

WPGraphQL for ACF seamlessly integrates Advanced Custom Fields with WPGraphQL.

Dropndot Video Library vs WPGraphQL for ACF