Raycast Extension Income for Developers: Honest Numbers from 2026

63 Raycast extensions have crossed the $1,000/month mark on the Pro tier store. That’s not a massive number — but it represents developers earning real recurring revenue from tools they built once, on weekends, without leaving their day jobs.

Key Takeaways

• Raycast’s Pro tier store pays developers 70% revenue share on paid extensions, with top earners pulling $800–$3,500/month
• First published extension typically takes 15–25 hours to build; time-to-first-dollar averages 4–8 weeks after launch
• The biggest income predictor isn’t code quality — it’s whether you solve a workflow problem that Pro users already pay to fix
• Active income (freelance Raycast work on Upwork/Contra) runs $65–$110/hr for experienced extension devs, but the market is thin

What the Raycast Pro Tier Actually Is

Raycast launched its monetization layer in late 2024, and by early 2026 it’s matured into a real ecosystem. The short version: developers publish extensions to the Raycast Store, Pro subscribers ($8/month or $96/year) unlock paid extensions, and you take 70% of every transaction.

The store runs on a one-time purchase model per extension, not subscription-per-extension. Typical paid extension price points sit at $2.99–$9.99. Do the math: at $4.99 with 300 paying installs, that’s roughly $1,047 in your pocket. Three hundred installs sounds modest. For a niche productivity tool aimed at developers, it’s achievable within 3–6 months if the extension solves a real problem.

What sells? The data from the public store rankings in 2026 points consistently to:

• API integrations that Pro users already pay for (Linear, Notion, Obsidian workflows)
• AI-augmented utilities that save 10+ minutes per day
• Niche developer tools with no mainstream alternative

What doesn’t sell? Generic stuff. A “search Google” extension. Anything with a free alternative two clicks away.

The Realistic Income Picture

Let’s break this into two tracks, because they’re genuinely different income types.

Passive track (store sales): Most first extensions earn $0–$80 in their first 30 days. That’s the honest number. You’re building an audience from scratch, and the Raycast store doesn’t have the discovery engine of the App Store or VS Code Marketplace yet.

The growth curve looks like this: slow for months 1–3, then a spike if you get featured or a prominent developer tweets about it, then a plateau. Extensions that land in the featured section of the Raycast store can see 500–1,200 installs in a week. That’s a one-time revenue event of $1,745–$4,196 at $4.99 — minus Raycast’s 30%.

Steady-state income for a well-maintained paid extension with decent SEO and word-of-mouth: $200–$1,200/month. The $800–$3,500 range I mentioned earlier applies to developers who have 3–8 published extensions, not one.

The boring middle: after launch, you’re responding to GitHub issues, releasing compatibility updates when Raycast ships API changes, and writing Twitter/X threads to keep the discovery pipeline alive. Figure 2–4 hours per week per active extension. It’s not passive in the “set and forget” sense. It’s more like owning a small product with low but real maintenance overhead.

Active track (freelance custom extensions): Some companies don’t want a public extension — they want something proprietary for their internal tools. Stripe integration with custom approval flows. A private Raycast extension for their internal wiki. This is freelance work, billed hourly or as a fixed project.

Rates for this on Contra and Toptal run $65–$110/hr for developers who can demonstrate shipped extensions. On Upwork, the market is thinner but exists — search “Raycast extension developer” and you’ll find occasional posts, usually from tech-forward startups. Project sizes typically run $500–$3,000 for a custom internal tool. Not a gold mine, but it stacks.

How to Actually Build Something That Sells

The extension itself is React + TypeScript. If you know those, the Raycast API surface is learnable in a weekend. Their docs at developers.raycast.com are genuinely good.

The harder part is picking what to build. Here’s the filter I’d use:

1. Does it serve a Pro user’s existing paid workflow? Pro users already spend money on tools. An extension that makes their Notion or Linear experience faster has a buyer who’s pre-qualified.
2. Is there a clear “10 minutes saved per day” story? That’s the pitch. Not “it does X” — “it saves you 10 minutes every day you work.”
3. Can you own a keyword in the store search? The Raycast store search is primitive in 2026. A well-named extension with the right tags can rank for niche queries with almost no competition.

For pricing, $4.99 is the sweet spot based on current conversion data. Below $2.99, buyers don’t feel the value signal. Above $7.99, you hit hesitation on a “launcher extension.” Save the $9.99 tier for genuinely complex tools with an obvious ROI story.

On capital requirements: essentially zero. You need a Mac, a Raycast Pro subscription ($8/month), and time. That’s it. This is one of the lowest barrier digital product plays available to developers in 2026.

On skill requirements: mid-level React knowledge plus API integration experience. If you’ve built a REST-connected frontend before, you’re qualified. You don’t need native Mac development experience — Raycast abstracts all of that.

The Comparison You Should Make

If you’re deciding between Raycast extensions and other digital product paths — VS Code extensions, Obsidian plugins, Chrome extensions — here’s the honest comparison:

• VS Code extensions: Larger potential audience, but monetization is immature. Open VSX and the Marketplace have no real paid tier in 2026. Sponsorware model works for a few, but income is inconsistent ($0–$400/month for most).
• Obsidian plugins: Community Plugins store has no native paid tier either. You’re relying on Gumroad or Patreon, which adds friction. Realistic income: $100–$600/month for a popular plugin.
• Chrome extensions: Crowded market, high churn, Chrome Web Store paid tier exists but conversion is poor for dev tools. More viable for consumer tools.

Raycast’s 70% rev share and growing Pro subscriber base (reportedly 180,000+ as of Q1 2026) makes it the strongest developer-tool monetization ecosystem right now. It’s not perfect — the audience ceiling is real — but the revenue-per-user math is better than anything else in this category.

Next Step

Go to developers.raycast.com/examples, pick one example extension that connects to an API you already use daily, fork it, and modify it to solve a specific workflow problem you personally have. This takes 3–4 hours on a Saturday morning. Publish it as a free extension first — the goal is just to get through the submission and review process, which averages 5–7 business days. Once you’ve shipped one free extension and seen how the store works end-to-end, converting it to a paid extension or building a second paid one becomes a concrete decision, not a hypothetical.

Photo by Marielle Ursua on Unsplash