Skip to content
indielist (beta)

Crush Crush vs Wallpaper Engine

Reviews on Steam

Wallpaper Engine

32.6× more reviews

Critical reception

Wallpaper Engine

9.2pp gap

Estimated sales (median)

Wallpaper Engine

17.4× more units (white-box estimate)

More recent

Wallpaper Engine

2 years apart

A

Crush Crush

2016 · Casual

Sad Panda Studios · Sad Panda Studios

Reviews
28,079
Positive
89%
Launch price
n/a
Engine
n/a
Sales (median)
2.1M
Net rev
$18.0M
B

Wallpaper Engine

2018 · Casual

Wallpaper Engine Team · Wallpaper Engine Team

Reviews
914,881
Positive
98%
Launch price
$4.99
Engine
n/a
Sales (median)
36.6M
Net rev
$104.3M

Tag overlap

40% shared , 8 shared tags, 12 only on Crush Crush, 12 only on Wallpaper Engine.

Only Crush Crush

Sexual ContentNudityFree to PlayHentaiDating SimClickerRomanceVisual NovelCasualComedyFemale ProtagonistResource Management

Shared

AnimeMatureCuteSingleplayerNSFWFunnyIndieMemes

Only Wallpaper Engine

UtilitiesSoftwareDesign & IllustrationAnimation & ModelingFirst-PersonActionEarly AccessPhoto EditingSandboxHorrorGamingGame Development

Sales estimates

Both estimates use the same vv1.0 multi-factor Boxleiter method. Click "How is this calculated?" on either to see the per-factor breakdown.

Sales estimate

vv1.0

1.3M to 2.9M

units (median: 2.1M)

≈ $10.8M to $25.3M net revenue (Steam cut + refunds + regional discount applied)

1.3Mmedian2.9M

Sales estimate

vv1.0

22.0M to 51.2M

units (median: 36.6M)

≈ $62.6M to $146.0M net revenue (Steam cut + refunds + regional discount applied)

22.0Mmedian51.2M

How comparison pages work

Verdicts are objective, they call out which game scores higher on a single measurable axis (reviews, price, sales estimate, recency). They don't claim "better." Tag overlap is computed from the public Steam tag list. Sales estimates use a multi-factor Boxleiter method whose formula is shown in full on each game's page.

Want a comparison that doesn't exist? Browse all games, find two slugs, and concatenate them: /compare/games/<slug-a>/<slug-b>. Both orderings render the same content; we canonicalise to alphabetical for SEO.