Asset Match by Pebblefold

A game can work on your machine and lose an image after it reaches itch.io. Asset Match's fictional example makes one possible cause concrete: the browser asks for textures/ball.png, but the ZIP contains textures/Ball.png. The difference is small enough to miss when you're checking a folder by eye.

The tool compares failed request URLs with the filenames in the archive you uploaded. After you confirm the hosting folder, it separates capitalization mismatches, missing entries, ambiguous matches and requests outside that folder. That gives a game creator a narrower place to investigate without treating every failed request as the same problem.

The useful restraint is what happens when the exact file exists. Asset Match leaves that failure unexplained. It doesn't claim to repair the upload, rewrite files or validate the whole game. A path check can rule out one explanation while leaving the actual loading problem open.

Pebblefold describes the tool as reading filenames locally in the browser, with no account, archive upload or HAR file required. This note is based on its public description, not a test with a game archive. A built-in fictional example offers a way to inspect the findings before selecting your own ZIP.

The current limit is 64 MiB and 2,000 archive entries, with index.html at the ZIP root. The itch.io listing discloses AI assistance in the code, graphics and text.