The SpreshApp Chrome extension is now open source. You can find the full code at github.com/PrashantBtkl/spreshapp_extension. If that's all you needed, go star it. The rest of this post is for anyone who wants context.
What the extension does
The Meta Ad Library is useful but it wasn't built for research workflows. Ads expire, links break, and there's no way to save or organize what you find. The SpreshApp extension solves the capture problem: it adds a "Save Ad" button to ad cards and detail pages inside the Ad Library. One click saves the creative, the copy, and the advertiser metadata to your SpreshApp account, where it's stored permanently and searchable.
The extension handles auth via Google OAuth, communicates with the SpreshApp API, and injects UI directly into Facebook Ad Library pages. It's a content script with a background service worker, nothing exotic, but the specifics matter when something running in your browser is talking to an external API.
Why open source
The short version: a Chrome extension that runs on Facebook pages and makes authenticated API calls should be auditable. You shouldn't have to take anyone's word for what it does.
The longer version is that I've been on the other side of this. Installing a browser extension from a company you've never heard of requires some trust, and that trust is easier to extend when you can actually read the code. Opening the source removes that friction entirely. Don't trust the privacy policy. Read the 600 lines of JavaScript.
There's also a practical benefit. The extension touches a moving target, Facebook updates its Ad Library layout, DOM structure, and CDN URL patterns regularly. Community fixes for these breakages are faster than waiting on a single maintainer to notice and push an update. If you've ever had the extension stop working after a Facebook change, open sourcing it means you or someone else can fix it and send a PR the same day.
Star the repo
If you use the extension or find the project interesting, a GitHub star helps with discoverability and is a good signal that the open-source decision was worth it.
github.com/PrashantBtkl/spreshapp_extension
How to contribute
The repo has issues open for known limitations, Facebook DOM changes that break detection, edge cases in the float button on detail pages, and a handful of UX things I haven't had time to get to. If any of those look tractable, pull requests are welcome.
The main constraint on contributions is that the extension needs to stay compatible with the SpreshApp API. Anything that touches the save flow or auth handling will need some coordination, but UI fixes, resilience improvements, and bug reports are straightforward.
What stays paid
The extension is the open layer on top of SpreshApp. The platform itself, AI analysis, permanent storage, team folders, MCP integration, remains a paid product. Opening the extension doesn't change the business model; it makes the trust problem go away for the part of the stack that runs in your browser.
If you save an ad with the open-source extension and want to do something useful with it, that's what the SpreshApp account is for.