Link Preview API - Free API to get Open Graph data, title & images for any URL
by•
Completely free.
Get back everything you need to render a rich link card in your app – the kind you see in Slack, iMessage, or Twitter when someone pastes a link.
Dedicated handling for popular websites like YouTube, Amazon, Twitter, Airbnb, SoundCloud, NYT, Vimeo, Giphy, and more. These return reliable, high-quality previews every time.
Built in image validation, and JavaScript rendering.
Works directly from the browser, no proxy server required.
Free usage up to 20,000 link previews.
Replies
genuinely useful and the 20k free requests is generous, but I'm curious about the business model rather than the technical side. proxy rotation and JS rendering at scale isn't cheap, so is this free tier subsidized by Exabase's paid platform, or is link preview itself expected to be a loss-leader that gets people into the rest of the product? just wondering what happens to reliability if this specific tool gets way more traction than the rest of the platform
Fabric
@galdayan That's a good and thoughtful question – we already operate this capability at scale for our other app (Fabric), so for the most part it costs us very little to provide this, and we do intend for this to be an entry point for people discover the other adjacent capabilities within the Exabase platform (deeper extraction etc.)
Really like the concept. Pulling this data is, in theory, simple enough. Until you hit an edge case and get blocked... or get junk content returned for no apparent reason. Can certainly think of places where this will be useful. Congrats on a strong product.
Fabric
Thanks @martin_tanner! Was really born out of necessity (we couldn't find anything reliable), and the internet is absolutely filled with wild variations and weird edge cases
Link previews always sit on that critical path between input and UI, so even small delays get noticeable fast.
How do you think about latency vs. completeness here?
Congrats on the launch!
Fabric
@jared_salois We think latency is super important – you can try it out here without signing up. In general, cache hits are almost instant (~100ms), and fresh fetches are around ~2s
The dedicated handling for Amazon, YouTube and friends is the part that actually earns the free tier, since generic OG scraping falls apart on exactly those. One thing I hit building preview cards: the og:image for a lot of big sites is a signed CDN link that expires, so a card you cached looks fine today and 403s the image tomorrow. Do you rehost or proxy the image so the preview stays stable, or hand back the origin URL as-is? That changes a lot for anyone caching results.
Simple APIs like this save more time than people expect. Open Graph previews are one of those tiny features that always become annoying to maintain manually.