Skip to content

Founder notes · 1 min read

Screenshot to Code Business Report: 80.8K GitHub Stars, $4,280 a Month

An open-source hit with 80.8K GitHub stars. Its hosted version makes $4,280 a month, and revenue is falling.

Screenshot to Code business report cover: 80.8K GitHub stars, MRR $4,280
← All articles
ODDIG · Business report · Screenshot to Code
Report v1 · Data as of 2026-11-10
Screenshot to Codescreenshottocode.com ↗ · open source, hosted

80,800 GitHub stars, $4,280 a month: what an open-source hit earns as a hosted product

One developer’s screenshot-to-code project went viral on GitHub in 2023. The paid hosted version has earned $263,571, but monthly revenue has fallen by about two-fifths while the stars kept climbing.

github.com/abi/screenshot-to-code
github.com/abi/screenshot-to-code, captured Nov 11, 2026
GitHub repository · captured 2026-11-11

Product at a glance

What it isUpload a screenshot, a mockup, a screen recording or a prompt and get front-end code in HTML/Tailwind, React or Vue.
Who it’s forFront-end developers, designers, freelancers and indie founders.
How it chargesHosted version: Hobby $15 a month, Pro $40 a month, half price yearly. The open-source code is free.
Business modelOpen-source project with a paid, credit-based hosted version.
Revenue, last 30 days
$4,008
MRR $4,280
Fact
GitHub stars
80.8K
MIT licensed
Fact
Paying per 1,000 stars
3.5
283 subscriptions
Derived
All-time verified revenue
$263,571
since November 2023
Fact
Revenue verified via Stripe on TrustMRR · synced 2026-11-11 00:24 UTCResearched 2026-11-11 · Oddig
ODDIG Business Report · Screenshot to Code · v1Data as of 2026-11-10 · Researched 2026-11-11
Quick read shows the scorecard, key findings, what to copy, our predictions and the bear case. Switch to Full report for the revenue charts, the GitHub star history next to revenue, pricing and channels.

Summary

What this business is

Screenshot to Code turns an image of a user interface into working front-end code using AI models. Abi Raja, a developer in New York, released it as an open-source project in November 2023, and it reached about 24,000 GitHub stars within weeks. Anyone can run the code with their own API key; the paid product is a hosted version at screenshottocode.com. It has taken $263,571 in verified revenue. Revenue averaged about $8,400 a month before December 2025 and about $5,100 a month since, while the repository kept gaining stars.

FormOpen-source repo + hosted web app
TeamOne founder
Entry price$15/mo
Founded2023-11-18
GitHub stars80.8K
Profit margin40% (TrustMRR)
ODDIG scorecard1 = weak · 5 = strong · our judgement, no total score
Revenue qualityHow much recurs
3/5
Channel spreadNot one channel
2/5
CopyabilityFor a solo founder
4/5
DefensibilityHard to copy the product
1/5
Evidence strengthHow sure we are
4/5
Share

Why these scores? See the reasons in Key takeaways →

Momentum

Declining. Revenue: last three complete months −16% on the three before; −15% on the same months half a year earlier.Derived

Best suited for

Builder (main). The project won attention by shipping fast and adding each new AI model as soon as it came out.

Creator (second). The audience is the repo’s followers, not paid marketing.

What you need to start. A plan for turning open-source attention into a paid product that stays ahead of the free version.Our read

Key findings

01Stars are not revenue80.8K GitHub stars and 283 paying subscriptions: about 3.5 per 1,000 stars.DerivedSee stars vs revenue →
02Stars up, revenue downThe repo kept gaining stars, while monthly revenue fell from about $8,400 on average to about $5,100, and 34% more since May.DerivedSee the revenue →
03Every generation has a costTrustMRR shows a 40% profit margin. Each credit calls a paid AI model.Our readSee the pricing →
Evidence tagsFactfrom a listed public sourceDerivedour arithmetic on factsFounderclaimed by the founder or siteOur readour judgement
01

Product overview

A free open-source tool, and a paid version you do not have to set up.

Screenshot to Code takes a screenshot, a design mockup, a screen recording or a text prompt and produces front-end code in stacks such as HTML with Tailwind, React or Vue, which can then be refined with plain-English follow-ups[1][3]. The open-source version on GitHub runs on your own machine with your own API keys for the AI models[3]. The hosted version at screenshottocode.com needs no setup and is paid[2].

The founder, Abi Raja, is a developer in New York; a third-party profile says he was previously a technical product manager at ADP and founded a startup called Patio[5]. TrustMRR lists the team as one person and the company as bootstrapped[1].

What the site looks like

screenshottocode.com
Homepage on desktop, captured Nov 11, 2026
Homepage on a phone, captured Nov 11, 2026
screenshottocode.com/pricing
Pricing page on desktop, captured Nov 11, 2026
Pricing page on a phone, captured Nov 11, 2026
github.com/abi/screenshot-to-code
GitHub repository on desktop, captured Nov 11, 2026
GitHub repository on a phone, captured Nov 11, 2026

Captured Nov 11, 2026 · Screenshots: screenshottocode.com and github.com.

What to look for

  1. 1
    The first line is a GitHub star count, 72,929, older than the 80.8K on GitHub itself.Fact
  2. 2
    “Build User Interfaces 10x Faster”: the hosted product sells speed, not the code, which anyone can run.Fact
  3. 3
    A GitHub button sits next to “Start Building”: the open-source repo is the credential.Fact

What to look for

  1. 1
    Two plans: Hobby $15 and Pro $40 a month, with yearly billing at half price.Fact
  2. 2
    Credits: one per generation or edit, reset monthly, no rollover.Fact
  3. 3
    No free plan. The free option is the open-source repo with your own API key. See §03.Our read

What to look for

  1. 1
    The repository: MIT licensed; TrustMRR lists the team as one person.Fact
  2. 2
    The README links to the hosted version, with tracking tags.Fact
  3. 3
    This page, not the product site, is where most people meet the project. See §04.Our read
PlanMonthlyYearlyCredits a month
Hobby$15$90 a year100
Pro$40$240 a year500

From the live pricing page, read Nov 11, 2026[2]. One credit per generation or edit; credits reset monthly and do not roll over; no refunds.

Our readThe paid product competes with its own free version. What a customer pays for is not the code but the convenience of not running it.Our read
02

Revenue analysis

About $134 a day from 283 subscribers, down from its first two years.

Oct 17, 2026
$240
Oct 13Oct 20Oct 27Nov 3

Hover or tap a bar. Verified daily revenue, Oct 13 – Nov 9, 2026 (UTC), from TrustMRR[1]. Blue: Saturdays and Sundays. Nov 10 is left out because the day was not complete at sync.

Share
Weekday average
$135

20 weekdays.Derived

Weekend average
$130

8 weekend days.Derived

Revenue ÷ MRR
0.94×

$4,008 in 30 days against $4,280 MRR.Derived

Profit margin
40%

As shown on TrustMRR.Fact

Monthly revenue: drifting down since May

May 2026
$6,478
$5.6K$3.8K$1.9K
DecJanFebMarAprMayJunJulAugSepOctNov

Hover or tap a bar. Monthly verified revenue from TrustMRR[1], December 2025 to November 2026. November covers Nov 1–10. Revenue before December 2025 totals $205,193.

Revenue quality
Revenue ÷ MRR
0.94×
MRR per subscription
$15.12
Share of all-time revenue
22% since Dec 2025
Verified record starts
Before Dec 2025
Typical monthly swing
9% a month

Our arithmetic on the verified data in this report. Revenue ÷ MRR uses the last 30 days; the share of all-time revenue counts the months in the chart above; the swing is the median change between complete months.

Monthly revenue peaked in this window at $6,478 in May 2026 and fell to $4,250 in October, down 34.4%[1]. Over the full record the decline is longer: the $205,193 earned before December 2025 averages about $8,400 a month across roughly two years, against about $5,100 a month since[1].Derived

Stars vs revenue

CapturedGitHub stars
Dec 202323,986
Mar 202438,831
Jul 202454,852
Jan 202567,203
Jun 202570,078
Jan 202671,429
Jun 202672,758
Sep 202677,255
Nov 202680.8K

From archived copies of the GitHub repository page[4] and the live page[3].

Dec 2023 → Jul 2024
+30,866

Stars in the first eight months after the launch month.Derived

Jan 2025 → Jun 2026
+5,555

Stars in seventeen months.Derived

Paying per 1,000 stars
3.5

283 subscriptions on 80.8K stars.Derived

Stars per paying customer
286

80,800 ÷ 283.Derived

Stars measure attention on GitHub, mostly from developers who can run the code themselves. They rose every year; revenue did not follow. The product site had 2,073 visitors and 14,888 Google search impressions in the last 30 days on TrustMRR[1].Our read

Market

Since 2023, large AI app builders such as v0, Lovable and Bolt have made generating an interface from an image or a description a common feature. We found no direct rival with verified revenue, so revenue is not compared.Our read

03

Pricing: credits on top of model costs

Two plans, priced in credits, because every request costs money.

Hobby
$15

100 credits a month.Fact

Pro
$40

500 credits a month.Fact

Yearly
50% off

$90 and $240 a year.Fact

MRR per subscription
$15.12

Close to the Hobby monthly price.Derived

MRR per subscription is $15.12, almost exactly the Hobby monthly price, and it was $15.31 in October[1][4]. The mix of plans behind that average is not public.Derived

Our readA credit price passes model costs to the customer, but the 40% margin shown on TrustMRR suggests much of each payment still goes to the AI providers.Our read
04

Where customers come from

GitHub first, and almost only.

Mainvisible on GitHubswipe →
GitHub repository
80.8K stars

Released in November 2023; reached about 24,000 stars within a month.[3][4]

Fact
README link
Hosted-version link

The README sends readers to the hosted version with tracking tags.[3]

Fact
New model releases
Same-day support

A third-party timeline lists GPT-4o and Claude 3.5 Sonnet support added right after release.[5]

Fact
Supportingvisible, impact not measurableswipe →
Search
14,888 impressions

Google impressions in the last 30 days, from TrustMRR’s Search Console link.[1]

Fact

What we could not read

We do not know how many paying customers first found the project on GitHub, or how many of the 80.8K stars belong to people who never ran it.

05

Growth strategies

Four moves, each visible from outside.

P1Launch as open source
What they didReleased the full tool on GitHub under the MIT licence.[3]
What happenedAbout 24,000 stars in the first month, 80.8K now.[3][4]Fact
How you can use itIf your tool is easy to explain in one image, release it openly and let developers spread it.
Cost & conditions Anyone can run it free; the paid product has to offer something more. 7-day test: publish a minimal open version of one feature and count stars and forks in a week.
P2Point the README at the paid version
What they didLinked the hosted product from the README.[3]
What happened$263,571 of verified revenue since launch.[1]Fact
How you can use itPut your paid offer where open-source users already are, in plain words.
Cost & conditions Most visitors want the free code; conversion is low. 7-day test: add one line to your README linking to a hosted version and track clicks.
P3Ship every new model fast
What they didAdded new AI models such as GPT-4o and Claude 3.5 Sonnet right after release.[5]
What happenedNot measurable from outside.Our read
How you can use itWhen your product depends on a fast-moving input, make being first with the new version your marketing.
Cost & conditions Constant upkeep for one person, and every model changes costs. 7-day test: write a short post the day a relevant new model or API ships, showing it in your product.
P4Sell credits
What they didPriced the hosted version in monthly credits, one per generation.[2]
What happenedMRR per subscription $15.12; 40% margin on TrustMRR.[1]Derived
How you can use itIf each request costs you money, price per use so heavy users pay more.
Cost & conditions Customers watch the counter; credits that expire can annoy them. 7-day test: list your cost per request and set a credit price at least three times higher.
06

Timeline

  • Nov 182023
    ProductFounding date on TrustMRR; the project goes viral on GitHub.[1][5]
  • Dec 12023
    MarketingAbout 24,000 stars.[4]
  • May2024
    ProductGPT-4o support; video-to-code follows.[5]
  • Jul 172024
    MarketingAbout 55,000 stars.[4]
  • May2026
    Revenue$6,478, the best month of the last twelve.[1]
  • Oct2026
    Revenue$4,250, down 34.4% from May.[1]
  • Nov 102026
    RevenueMRR $4,280 from 283 subscriptions; 80.8K stars.[1][3]
07

Key takeaways

Screenshot to Code shows what a viral open-source project can earn on its own: a real business at launch, then a slow decline once the free version and bigger rivals catch up.

Why we scored it this way

ODDIG scorecard1 = weak · 5 = strong · our judgement, no total score
Revenue qualityHow much recurs
3/5
Regular monthly subscriptions, revenue at 0.94× MRR. But revenue is about two-fifths lower than in its first two years.Derived
Channel spreadNot one channel
2/5
Almost everything starts on GitHub. The product site had 2,073 visitors in 30 days on TrustMRR.Our read
CopyabilityFor a solo founder
4/5
One person built and runs both the repo and the hosted app. The hard part is the viral launch.Our read
DefensibilityHard to copy the product
1/5
The code is MIT licensed and free to run, and large AI app builders now do the same job.Our read
Evidence strengthHow sure we are
4/5
Full verified revenue since launch and eight archived star counts. Monthly figures before December 2025 are not public.Our read
Share

Copy

  1. Ship the open-source version first and let GitHub do the launch. P1
  2. Link the hosted version from the README. P2
  3. Add each new model on release day; it gives the repo a reason to trend again. P3
  4. Charge in credits when every request costs you money. P4

Avoid

  1. Treating stars as a revenue forecast. 3.5 payers per 1,000 here. §02
  2. A hosted product with nothing the free version lacks. §09
  3. Ignoring model costs in your price. The margin here is 40%. §03
08

Our predictions

Three claims with dates. We mark each one right or wrong on its date and keep the result on the page.

#PredictionCheck onStatus
#1
November verified revenue lands between $3,300 and $4,600TrustMRR, $4,250 in October and $1,193 in Nov 1–10.
Dec 1, 2026Open
#2
MRR is below $4,280TrustMRR MRR, $4,280 on Nov 10, down 3.7% in 30 days.
Jan 31, 2027Open
#3
The repository passes 82,000 starsGitHub, 77,255 in September and 80.8K on Nov 11. Stars keep rising without lifting revenue.
Jan 31, 2027Open

Track record: the predictions in our earlier reports are still open; the first checks land Dec 1, 2026. We mark each prediction right or wrong on its date and keep the result on the page.

09

What could prove us wrong

Things that would change our read, and how to check them.

  1. A new model could restart growth. Past model launches gave the project new attention.Check: monthly revenue after the next major model release.
  2. The 40% margin is a profile figure. We could not see the costs behind it.Check: not public.
  3. Paid users may come from search, not GitHub. TrustMRR shows 14,888 Google impressions in 30 days.Check: not public; no traffic split.
  4. A sale may be in progress. The TrustMRR profile mentions what a sale would include, though it is not listed.Check: the TrustMRR listing on the next review.

Appendix

FAQ

How much does Screenshot to Code make?

$4,008 in the 30 days to Nov 10, 2026, verified through Stripe on TrustMRR. MRR is $4,280 from 283 subscriptions; all-time revenue is $263,571.

Is Screenshot to Code free?

The open-source code on GitHub is free under the MIT licence if you bring your own AI API key. The hosted version costs $15 or $40 a month, or half that billed yearly.

How many GitHub stars does Screenshot to Code have?

About 80.8K on Nov 11, 2026. It had about 24,000 in December 2023, a month after release.

Who built Screenshot to Code?

Abi Raja, a developer in New York, under his company WhimsyWorks, Inc. TrustMRR lists the team as one person.

Sources

  1. [1]
    TrustMRR: Screenshot to Code — revenue, MRR, subscriptions, daily and monthly data, visitors, search impressions and profit margin. Verified through a Stripe API key. Synced 2026-11-11 00:24 UTC.
  2. [2]
    screenshottocode.com — homepage and pricing page. Read 2026-11-11.
  3. [3]
    GitHub: abi/screenshot-to-code — stars, licence and README. Read 2026-11-11.
  4. [4]
    Wayback Machine captures of the GitHub repository from December 2023 to September 2026, and of the TrustMRR page on Oct 15, 2026 — star counts and MRR on those dates. Read 2026-11-11.
  5. [5]
    EveryDev: WhimsyWorks — third-party profile with the founder’s background and product timeline. Read 2026-11-11.

Screenshots © WhimsyWorks, Inc. and GitHub, used for commentary. Oddig has no business relationship with Screenshot to Code. Numbers change daily; check the sources for the latest.

The projects worth a look, in your inbox.

New reports like this one, what is for sale, and who is holding up or fading.

Free. Unsubscribe any time.

The discussion

Comments are closed for this article.

Still building?

Get the next useful signal in your inbox.