Wallpaper Engine vs We Were Here Too
Reviews on Steam
Wallpaper Engine
83.3× more reviews
Critical reception
Wallpaper Engine
19.4pp gap
Cheaper at launch
Wallpaper Engine
$5.00 cheaper
Estimated sales (median)
Wallpaper Engine
47.6× more units (white-box estimate)
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
We Were Here Too
2018 · Adventure
Total Mayhem Games · Total Mayhem Games
- Reviews
- 10,985
- Positive
- 79%
- Launch price
- $9.99
- Engine
- n/a
- Sales (median)
- 769K
- Net rev
- $4.4M
Tag overlap
15% shared , 3 shared tags, 17 only on Wallpaper Engine, 17 only on We Were Here Too.
Only Wallpaper Engine
MatureUtilitiesAnimeSoftwareDesign & IllustrationAnimation & ModelingNSFWMemesCuteActionSingleplayerFunnyEarly AccessPhoto EditingSandboxGamingGame Development
Shared
First-PersonIndieHorror
Only We Were Here Too
Online Co-OpEscape RoomPuzzleCo-opMultiplayerInvestigationAction-AdventureAtmosphericAdventureMultiple EndingsCo-op CampaignMysteryPsychological HorrorLinearCasualDarkImmersive
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.022.0M to 51.2M
units (median: 36.6M)
≈ $62.6M to $146.0M net revenue (Steam cut + refunds + regional discount applied)
Sales estimate
vv1.0461K to 1.1M
units (median: 769K)
≈ $2.6M to $6.1M net revenue (Steam cut + refunds + regional discount applied)
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.