The hidden costs of self-publishing on consoles

By Artem Shkafenko, Head of Marketing at Upscale Studio.

There is a growing trend among indie developers to skip publishers and self-publish directly to consoles. I work in console publishing, and I often see solo developers asking: “Why should I share revenue with a publisher? I can just buy a devkit and release it myself on Switch/Xbox/PS to keep 100% of the profit.”

The short answer is: Yes, you absolutely can. And if you are tech-savvy, you probably should.

However, many developers calculate the hard costs (hardware), but ignore the soft costs (time and opportunity cost).

I wanted to share a realistic breakdown of the numbers for the DIY route, so you can budget your runway accordingly.

1. The Hard Cash (It’s not just $100)

Getting onto consoles isn’t as cheap as Steam’s $100 fee.

• Devkits: Due to strict NDAs, I cannot disclose exact prices. But to get a full suite of hardware (Nintendo + Sony + Xbox), you are looking at the equivalent of roughly 963 Big Mac Meals.
• Legal Entity: You can’t sign Sony/Nintendo contracts as a “guy with a gmail account”. You need a properly registered company (LLC/Ltd). Setup cost: $500 – $1,500 + annual accounting fees.
• Ratings: While IARC is free for digital, if you target Japan (CERO) or physical releases, costs increase.

2. The Hidden Tech Debt (1-3 Months approximately)

This is where most budgets die.

• Controller Support (40-60 Hours): It’s not just mapping buttons. You need to rewrite your entire UI navigation logic. Can the player navigate the inventory without a mouse? What happens if the controller disconnects mid-fight? (TRC Requirement).
• Save Systems (20-30 Hours): Consoles handle save data differently from PC. You have to use their async APIs. If you block the main thread while saving or fail to handle a “Storage Full” error gracefully, you fail certification.
• Font & UI scaling (20 Hours): What looks good on a 1080p monitor is unreadable on a 720p Switch Lite screen. Nintendo requires specific font legibility. You will likely need to redesign your GUI.

3. The Certification Loop

Passing Cert (Lotcheck/TRC) is the final boss.

• There are 400+ specific requirements on the checklist you need to verify.
• The Wait Time: If you fail one critical check, you are rejected. You fix it, resubmit, and wait. The queue for review can take 5 to 10 business days.
• The Reality: Most first-time indies fail certification 2-3 times. That is 4-6 weeks of just waiting, unable to launch.

4. The Opportunity Cost Math

Let’s calculate the real damage.
Suppose your burn rate (rent, food, internet) is $2,000/month.

If you decide to port yourself, and you’ve never done it before, plan for 3 months minimum (Learning SDKs + Coding + Certification Loops).

The Equation:

$2,000 x 3months = $6,000 of your lifetime spent reading PDFs instead of making games.

Plus, you delay your revenue by 3 months. If your game would make $1,000/month, you just lost another $3,000 in potential sales.

Conclusion

My goal isn’t to discourage you. Learning to port is a valuable skill! But make sure you value your time as much as your money.

About the Author: Artem Shkafenko, Head of Marketing at Upscale Studio, a porting and publishing house specializing in bringing PC indie games to consoles. 

If you have a project you want to bring to consoles, submit your pitch here: https://upscale-studio.com/#contact