Launching today
Link Preview API
Free API to get Open Graph data, title & images for any URL
20 followers
Free API to get Open Graph data, title & images for any URL
20 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
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?