webMAN MOD: what an all-in-one PS3 homebrew plugin actually bundles

A fork of webMAN that competes with itself by including everything

webMAN MOD started as a fork of DeanK's original webMAN plugin for the PlayStation 3 and has grown into a bundle. The stated goal is an AIO plugin, meaning one package that gathers features otherwise spread across the PS3 homebrew scene into a single interface. The primary language is C, and the licence is GPL-3.0.

What lands in the bundle covers the ordinary media cases and a few things nobody else bothers with. For storage there is an FTP server with remote shutdown and restart, a WWW server that adds mount, eject and cpursx control, NTFS support for PS3 and PS1 games plus Blu-ray movies and DVD video in ISO form, and netiso for loading games over the network in ISO or JB folder form. A file manager, a gamepad emulation layer, ps3mapi, task automation and a memory debugger complete the list.

The interesting engineering decision is not any one of these but the packaging. Competing plugins exist for each category, so the value depends on whether you would rather configure once and lose the ability to remove individual pieces. webMAN MOD does not read like a modular system, it reads like a single binary that grew by accretion.

The firmware support matrix is the real documentation

Because this is console homebrew, support is expressed as a firmware matrix rather than a package list. The README covers custom firmwares with the Cobra feature enabled from version 4.46 to 4.93 in CEX, DEX and DECR, Evilnat firmware from 4.87.2 to 4.93 including PEX and D-PEX variants, and REBUG firmware both with Cobra enabled and with it disabled through Mamba loaded via `boot_plugins_nocobra_kernel.txt`.

Further down the list, PS3HEN is supported on 4.82 to 4.84 OFW in CEX and DEX and on 4.84 to 4.93 HFW, while classic custom firmware with Mamba loaded via IRISMAN, with Mamba or PRXLoader, or with PRXLoader alone is covered from 3.41 to 4.93. Hardware coverage follows the same pattern: all PS3 models including fat, Slim 20xx, 21xx, 25xx, 3xxx and SuperSlim 4xxx are supported through the PS3HEN payload, while models that can be downgraded to 3.56 or lower are supported via BGToolset or PS3Xploit Flash Writer.

One line in that matrix is a trap for anyone building from source. To support firmware 4.70 and lower, the project must be recompiled without `LAST_FIRMWARE_ONLY` in `flags.h`. A default build therefore silently drops support for older firmware. The README also flags itself as unfinished, so treat the matrix as approximate.

Installing from the XMB menu rather than from a shell

There is no documented command line install in this project, and the README does not give one. Installation is described in terms of the console itself: the plugin ships as a PKG for the PS3, the repository carries build scripts such as `_Make_pkg.sh` and `_Make_pkg.bat` for producing one, and an installer with four editions is offered, full, lite, standard (rebug) and nonCobra.

Once installed, updates do not need a computer. A built-in online updater is reachable from the XMB menu, which is the part that matters for a plugin you will keep for years. The VSH menu integration appears when you hold SELECT, and the sLaunch GUI opens with START or R2+L2 on the XMB. An FPS counter overlay toggles with L3+R3.

For a first real use, the shortest path is the browser rather than the disc. The README documents a Coverflow web GUI at `/games.ps3` aimed at phones and desktops, a grid GUI at `/index.ps3` with resizable icons that can filter by type, device or name, and temperature pages at `/cpursx.ps3`, `/cpursx.html`, `/tempc.html` and `/tempf.html`. Installing packages from any folder is done with the web command `/install.ps3<path>`.

Two GUIs for the same game list, and why the grid filters matter

The plugin exposes the same content twice, which is a deliberate choice rather than duplication. `/games.ps3` is a Coverflow interface built for touch screens and short sessions, while `/index.ps3` is a grid with resizable icons that a desktop browser can use properly.

Cover art resolution is the part most users will actually configure. The Title ID is read from the ISO filename or from the JB folder name, and covers can be rendered as discs, from `ICON0.PNG`, or pulled from the multiMAN, IRISMAN or ManaGunZ repositories, or from a file sitting next to the ISO. There is an option to display online covers using a free service provided by DeViL303, and an option to show either the original filename or the title parsed from `PARAM.SFO`, with localized titles available where the PARAM.SFO carries them. The plugin is translated into 23 languages.

Filtering is what keeps large libraries usable. The grid can be filtered by type, device and name, and unwanted entries are excluded through `wm_ignore.txt`, which accepts file names and Title IDs. A custom `wm_custom.xml` menu can be injected into the games menu, and the `home` path can be pointed at `app_home/PS3_GAME` so that unmounting a game returns you to multiMAN, IRISMAN or the Rebug Toolbox rather than the XMB.

Where webMAN MOD is the wrong choice

The clearest limitation is compatibility: on OFW, the README lists PS3HEN support for 4.82-4.84 CEX and DEX. Other documented configurations use custom firmware, Mamba, PRXLoader or a hardware downgrade, so an unsupported console will not work. That is a fact about the platform rather than a defect in the code, but it makes the adoption decision a one-time decision.

The second limitation is blast radius. A memory debugger, a shell that can trigger cpursx and eject operations over HTTP, and an FTP server with remote shutdown are all inside the same binary. If you only need to mount ISO files, this is a heavy way to get there, and the HTTP surface in particular is one you have to think about on a home network. The README does not document access control for the web server, so treat the URLs as local-only unless you have verified otherwise yourself.

Documentation is the third gap. The README states outright that it is still in progress, the main command and behaviour documentation lives in the GitHub wiki rather than in the repository, and the separately advertised deepwiki page is described by the project itself as containing details that are not very accurate.

Against standalone plugins and against the original webMAN

The closest comparison is not another project, it is the plugin this one was forked from. DeanK's webMAN and sMAN cover the core cases: FTP, a web server, ISO and folder browsing, netiso, NTFS, fan control and PAD shortcuts. webMAN MOD keeps all of those, marked in the README as the vanilla sMAN and webMAN feature set, and adds the installer, the online updater, the web GUIs, localization into 23 languages and the extended system information page.

That split tells you when to choose which. If you already run original webMAN and everything works, the argument for moving is the Coverflow and grid interfaces, the built-in updater and the release cadence, which produced 1.47.50 on 2026-10-10 after 1.47.48t on 2025-03-07 and 1.47.47n on 2024-11-14. If you want the smallest plugin that mounts games over the network, the original remains the smaller answer.

Standalone plugins for single jobs, such as a dedicated netiso host or a dedicated file manager, are the other comparison. Bundling avoids running several services and removes the need to remember several hotkey combinations, at the cost of any ability to update one component independently.

Editorial conclusion

Pick webMAN MOD if you run custom firmware on a PS3 and want one plugin instead of several, and accept that support depends on matching firmware family. Leave it alone if your console falls outside the documented firmware support matrix or you want the smallest possible privilege footprint. Before installing, check the firmware support matrix in the README against your exact version, and for firmware 4.70 or lower remember that `flags.h` must be recompiled without `LAST_FIRMWARE_ONLY`.

Frequently asked questions

Official sources

1. aldostools/webMAN-MOD on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases