Launched this week
Link Preview API
Free API to get Open Graph data, title & images for any URL
239 followers
Free API to get Open Graph data, title & images for any URL
239 followers
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.
Fabric
Hey Product Hunt 👋
I'm Johnny, founder of the team behind the Link Preview API.
We built this because for such a simple thing, it's extremely tedious and painful to cover all of the weird edge cases on the internet, and it shouldn't be something you need to pay for when starting out.
So we decided to make something radically simple... and completely free, up to 20,000+ requests per month.
Just send a GET request with any URL and get back everything you need. Get structured JSON with the title, description, og:image, favicon, image dimensions, and site name.
We handle all of the headache-inducing proxy-rotation, JavaScript rendering and more, including purpose-built integrations for YouTube, Amazon, Twitter, and a fair few other sites that need special treatment.
Link Preview is part of the broader Exabase platform, so the same API key also gets you full page extraction, document parsing, and deep search if you ever need to go further. But it works perfectly well on its own.
Thanks for taking a look – I'll be here all day to answer your comments!
Johnny
@johnny_makes congrats on the launch johnny! the "completely free up to 20k requests" is a smart move for getting devs to actually try it without friction. curious how you're handling the sites that actively block scrapers, does the proxy rotation cover most of those?
This is one of those “simple until you actually build it” problems. We’ve had to think about link previews, favicons, og images, and weird URL edge cases while building our product, and it gets messy very quickly. every site seems to have its own little way of breaking the “just fetch the metadata” idea :)
The dedicated handling for sites like YouTube, Amazon, Twitter/X, Airbnb, etc. is probably the real value here. reliable previews matter a lot when the link card is part of the product experience, not just a nice extra. Also, 20,000 free previews is pretty generous for builders starting out. Curious how you handle websites that block scraping or return different metadata depending on JS/user-agent/location. does the API normalize that automatically, or do developers still need fallback logic?
Fabric
@andrasczeizel Absolutely, this is our battle-tested API that powers our own apps, so it was important to us that it handles all cases elegantly and avoids users seeing any failed fetch scenarios. We have built-in quality control measures that ensure that preview writes are always of sufficient quality, and we have a >95% success rate across the web.
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.)
me getting twenty thousand free previews makes this easy to test in real projects. will you add custom cache controls? that could help developers refresh updated page content faster.
Fabric
@advin_jadis That's great feedback, I've made a note to add it to the near-term roadmap
Having just spent time on the other side of this (getting OG tags, sitemaps and canonicals right for my own SaaS), I appreciate how much invisible work goes into making previews "just work." The per-site handlers for YouTube/Amazon/etc. sound like the honest solution. Question: how do you handle cache freshness? If a site updates its og:image, how quickly does the API reflect that — and can callers force a refresh?
Fabric
Hey @kojimajunya, good question! We periodically recrawl and refresh the cache, but the idea of allowing a force-refresh option is great feedback, we'll add that to our roadmap
Voquill
This solves a surprisingly annoying problem. Congrats on the launch!
How reliable is it when sites change their metadata or introduce new anti-bot measures?
Fabric
Thanks @henry_habib! We built it specifically to handle all these kinds of painful cases, and it has built in proxy rotation and a 95%+ success rate
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