Demake

What it does

Demake converts images into retro game console ROMs and sprite sheets that comply with specific hardware constraints. The tool targets 8-bit and 16-bit era consoles and handhelds. It includes a web UI, CLI, and NPM package. The core insight is that generative AI can produce retro-styled graphics but often violates the exact pixel and color limits of actual hardware. Demake bridges that gap by processing images through hardware-specific rules.

Who it is for

Game developers building for classic consoles or emulating that aesthetic. Fan game creators. Hobbyists working with retro hardware. Developers who want to automate sprite conversion rather than manually constrain assets. Anyone generating retro art with AI tools who needs output that actually runs on target systems.

Pricing

The site does not show prices.

How it stands out

Demake ships with a custom declarative language called Demotic designed to express retro game projects without implementation detail. Instead of pixel-perfect absolute coordinates, developers use relative units like vw, vh, vmin, and vmax—borrowed from web CSS. This allows the same code to adapt across different console specifications. The tool runs entirely in the browser with no server upload, addressing privacy and latency concerns. It targets not just one console but multiple platforms, making it useful for creators wanting to port a project across systems.

What a founder should check

First, understand the incumbent tools and workflows. Existing sprite editors, pixel art programs, and console-specific development kits already handle image conversion. Verify whether developers actually struggle with AI-generated assets violating hardware constraints enough to justify switching tools, or whether current pixel art pipelines handle this adequately.

Second, assess the switching cost and tooling ecosystem. Demotic is a new language. Evaluate whether learning it and integrating it into existing developer workflows (which may already rely on established tools like Aseprite, PyGame, or console SDKs) creates enough friction to limit adoption. Check whether the relative units approach adds real value versus absolute pixel constraints.

Third, examine the moat and competitive pressure. The core technology—image-to-hardware conversion—is not novel; tools like GIMP and specialized converters already exist. The differentiation rests on the declarative language and multi-platform support. Verify whether these features are defensible or whether larger developer tool companies could quickly add similar functionality to existing platforms. Also check whether the retro game development market is growing fast enough to sustain a specialized tool versus shrinking as hobbyist interest wanes.