One API for native embeds and intelligent fallback
Iframely excels at provider coverage for known platforms. OpenGraph.io adds a third resolution tier, a hosted fallback card built from page metadata, so arbitrary URLs still return useful embed output instead of failing.
OpenGraph.io vs Iframely
OpenGraph.io supports fallback embeds for URLs outside the native provider ecosystem, plus link preview metadata on the same platform.
| Capability | OpenGraph.io | Iframely |
|---|---|---|
| Native oEmbed providers | Yes: YouTube, Vimeo, Twitter/X, and more | Yes: extensive provider network |
| oEmbed discovery links | Yes | Yes |
| Fallback for arbitrary URLs | Yes: hosted OpenGraph card (og_frame) | Limited: primarily provider-list based |
| source field (native / discovery / fallback) | Yes | Varies |
| embed_id + refresh API | Yes | Varies by plan |
| Link preview metadata (same platform) | Yes: Site / Unfurl API | Separate products or add-ons |
| ?url= query parameter | Yes | Yes |
| Self-hosted option | Cloud API | Self-hosted available (open source) |
CMS & editor integration guides
Drop OpenGraph.io embeds into the editors and CMS platforms your team already uses.
FAQ
For many oEmbed workflows, yes: swap the API URL and use the html field. OpenGraph.io adds a fallback tier Iframely does not emphasize: hosted cards for URLs outside the provider network. Review the migration guide for response field mapping. See the Migration guide.
Iframely maintains a larger curated provider list. OpenGraph.io focuses on native providers plus discovery, then generates a fallback card for everything else, which is often the harder problem in production UGC and CMS workflows.
OpenGraph.io is a hosted API. Iframely offers self-hosted open-source software for teams that want to operate their own infrastructure.
Point your oEmbed requests at OpenGraph.io, pass your app_id, and use ?url= for the target. See the step-by-step migration guide for code examples and field mapping. See the Migration guide.