Martin: No Filter Fighters on Android
There is no official Android APK. Anyone offering one is repackaging someone else's work — and the browser version already plays the full game, at full speed, without an install.
Play it on Android in four steps
- Open this site in Chrome. Chrome handles HTML5 games better than most Android browsers, and the game's touch layer is built around it.
- Press Play and give it a few seconds. The first load pulls the game files. On mobile data that can take longer than on Wi-Fi; after the first load the files are cached.
- Turn the phone sideways. The game is designed for landscape. In portrait the play area is too narrow and the touch buttons overlap the action.
- Tap once on the play area. Touch controls appear automatically, but they need the game canvas to have focus first.
Make it feel like an app
Chrome can pin the page to your home screen, which removes the address bar and opens straight into the game:
- Open the page in Chrome.
- Tap the three-dot menu, then Add to Home screen.
- Launch it from the new icon. It opens in its own window rather than a browser tab.
Why there is no APK
The creator publishes the game as an HTML5 build plus Windows, Linux and Steam Deck downloads. Android is not on the list. The game is a free, non-commercial fan project, and repackaging it into an APK would break the terms it was released under.
If you see a site offering a "Martin No Filter Fighters APK", treat it as unverified at best. Sideloaded packages from fan-game download pages are a standard vehicle for adware, and there is nothing in them you cannot get by loading this page.
PS5, Xbox and Switch: there is no console version
The same answer covers every console. There is no PlayStation 5, Xbox Series X/S or Nintendo Switch build of Martin: No Filter Fighters — no store page to wishlist and no announced port. People searching for a "Martin fighting game PS5" release are looking for something that does not exist.
What does exist is the browser build on this site, which runs on any modern phone, tablet, Mac or PC, plus the free Windows, Linux and Steam Deck downloads on the creator's itch.io page. If a console version ever appears, it will be announced there first, because that listing is where the developer posts every build.
Touch controls feel wrong?
- Buttons too small: rotate to landscape and use fullscreen.
- Character keeps walking: a touch is stuck. Tap the play area once to reset focus.
- Controller instead: a Bluetooth gamepad works. Pair it, then press any button once so the game detects it — the touch layer hides itself when a controller is connected.
Older or low-end phones
This is a 2D fighter but the browser build still loads a sizeable engine bundle. On a phone with limited RAM, close other tabs before starting — background tabs are the usual reason a browser game stutters on Android. If it still runs poorly, the Windows build on the creator's page is the more reliable option on a PC.
How much data does it use
The browser build downloads its engine and game assets the first time you play. The boot page alone is roughly half a megabyte, and the engine and assets are considerably larger than that. We have not measured the total transfer for a full session, so treat any specific number you see quoted elsewhere as unverified.
What that means in practice: play on Wi-Fi the first time. After the first load the browser caches most of it, so repeat visits are much lighter. If you are on a metered plan, do not clear site data — clearing it forces the whole download again.
Does it work offline
Not reliably. The game is served from the developer's host, and the browser only keeps what it has cached. If you lose connection mid-session the game will usually keep running on what is already loaded, but starting a fresh session offline is not something we can promise.
If offline play matters to you, the developer's Windows build is the honest answer — it is a local executable with no network dependency. The Android path is a browser path, and it behaves like one.
Saving it to the home screen: what actually changes
Pinning the page to your home screen opens it in its own window, without the address bar. That gives you roughly an extra strip of vertical space, which on a flipped phone is meaningful for a fighting game.
It does not make the game an installed app. It is still a browser view, it still needs a connection for the first load, and it still updates whenever the developer ships a new build. The benefit is screen real estate and one-tap access, nothing more.
Screen size and aspect ratio
Fighting games are wide. On a 20:9 phone held sideways, the game fills the height and leaves black bars at the sides, or fills the width and crops. Either way you are not getting a desktop-shaped picture.
The practical advice is to use the game's own fullscreen button once you are in a match rather than relying on the browser's. It scales the canvas to the device instead of letting the page control the framing.
On a tablet the situation reverses: you have plenty of width, and the touch buttons end up far apart. Two hands on the edges of a 11-inch tablet is a genuinely comfortable way to play this, arguably better than a phone.
Audio on Android
Mobile browsers block audio until the page receives a real user gesture. Tapping Play counts as one, but if the browser was resumed from the background it may have suspended the audio context again. If you get picture but no sound, tap inside the game once — that re-arms audio without restarting the match.
Also check the media volume, not the ring volume. Android keeps them separate and it is a common five-minute confusion.
Battery and heat
A fighting game running in a browser is a sustained load. On a mid-range phone you should expect the device to get warm and the battery to drop faster than during video playback. Closing other tabs before you start is the single most effective thing you can do — background tabs consume memory the game needs, and Android is aggressive about killing them mid-session, which manifests as a sudden reload.
What about iPhone
The same browser path works, but the details differ: Safari handles gamepad support less consistently than Chrome on Android, and adding a page to the home screen behaves differently. We have not tested the iOS path, so treat it as unverified rather than recommended.
Three things that decide whether Android play works
Memory, not CPU
A 2D fighting game is not demanding on a modern phone's processor. What actually fails is memory: the browser needs room for the game plus the page plus every other open tab. Closing tabs before you press play fixes more Android problems than any setting.
Browser choice
Chrome handles this build best. Some Android browsers throttle background timers and suspend audio contexts more aggressively, which shows up as stuttering or silent audio rather than an obvious error. If the game misbehaves, the first test is always "open it in Chrome".
Orientation lock
If your phone keeps rotating back to portrait mid-match, the game area resizes and you lose the fight to the layout rather than to your opponent. Turning on orientation lock before you start is worth the two seconds.
Keep reading about Martin: No Filter Fighters
If Android works but you want to understand the game itself, the full Martin: No Filter Fighters roster explains what each of the eleven fighters is built around. The control list covers the same keys on a desktop keyboard, and the help page handles everything that is not Android-specific.
When Android genuinely is not enough
If the game stutters, the touch layout fights you, and the screen is too small to read the health bars, the honest recommendation is the desktop build. The developer ships Windows, Linux and Steam Deck zips. A phone is a good place to try this game; it is not the best place to get good at it.