Whether skin changers are bannable, whether they're safe, what happens in ranked, and why your skins break on patch day. No hedging, no marketing — including the parts that aren't in our favour.
Short answer: custom skins are against Riot's Terms of Service, nothing is ever ban-proof, and you use a skin changer at your own risk. Anyone telling you otherwise is selling something.
The longer answer is that in practice Riot has historically aimed enforcement at tools that hand you a competitive advantage — scripts, automation, cheats — rather than purely cosmetic, client-side mods that only change what renders on your own machine. Riot has never published a guarantee in either direction, and that ambiguity is the actual risk you're accepting.
Chud takes the conservative position on your behalf: skin injection is blocked in Ranked Solo/Duo and Ranked Flex by default, and in any game whose queue can't be positively identified.
Chud is free and open source, so the code can be audited by anyone. On top of that:
127.0.0.1 — the local API Riot exposes for companion tools.cslol-dll.dll by SHA-256 and refuses it if the file changes after first use, so a silently swapped DLL gets rejected as possible tampering.The honest residual risk is the Terms of Service risk of running custom skins at all — see the question above.
Not with Chud's default settings, and we'd recommend leaving it that way. "Block in ranked" is on out of the box and refuses skin injection in Ranked Solo/Duo and Ranked Flex. Any game whose queue can't be positively identified is treated exactly like ranked.
The check is fail-closed: every injection side effect passes through one policy gate immediately before it runs, and if live state can't be verified, injection is denied rather than allowed. A background safety monitor runs the whole time Chud is open, regardless of which tools you've armed.
Auto-accepting the ready check goes through Riot's official local client API — the documented interface Riot exposes for third-party companion apps — rather than faking mouse clicks or reading game memory. It's the lowest-risk thing Chud does, and it works completely independently of skins: you can run auto-accept and never enable skin injection at all.
Install Chud and start League — it finds the running client by itself, nothing to configure. Skins need one extra file, once: for legal reasons Chud can't ship the skin-injection library, so you drop your own copy of cslol-dll.dll into %LOCALAPPDATA%\Chud\cslol-tools\.
The Skins tab shows a setup card with Open folder and Re-check buttons until the file is there, so you never have to hunt for the path — and the file survives every update, so this is genuinely a one-time step. After that, open champ select, click the launcher pill in the bottom-right of your client, and pick any skin for the champion you locked in. Full walkthrough in the docs.
Yes — client-side custom skins still work. But every League patch can change the game files mods target, which is why skins routinely break on patch day and need the tooling to catch up.
Chud updates itself, so when a patch lands you get the fix without going hunting for a fresh download.
Patch-day breakage is normal. Work through this order:
cslol-dll.dll is a current build. If you deliberately replaced it and Chud now refuses it, delete %LOCALAPPDATA%\Chud\state\cslol_dll.trust so the new copy can be re-trusted.Still stuck? There's a full patch-day troubleshooting walkthrough here, the docs go deeper, and the Discord is the fastest place to get eyes on it.
No — Chud is Windows only (Windows 10 and 11). There's no macOS build, and the injection approach custom-skin tools depend on doesn't work against the Mac League client. This isn't a "coming soon" — it's a platform limitation.
No. Custom skins are purely client-side — they change only what's rendered on your machine. Enemies and random teammates see the default skin.
The one exception is friends in your lobby who also run Chud: party sync lets everyone in the lobby see each other's skins and announcers, auto-detected, with no codes to paste.
Completely free. No paid tier, no ads, no account. It's open source on GitHub, the installer is about 12 MB, and it installs for your user only — no administrator rights needed.
CSLOL Manager is a mod installer: you source .fantome files yourself, import them, tick a list, and hit run before you play.
Chud is built around champ select — a launcher pill appears the moment champ select opens, so you pick a skin for the champion you actually locked in. Around that: a searchable library of community skins, malware scanning on every download, an announcer pack builder, automatic party sync, auto-accept, and the ranked kill-switch.
Both rely on the same open-source injection library, which is exactly why Chud asks you to supply cslol-dll.dll once. There's a fuller side-by-side comparison here, along with why skins break on patch day.
Yes — source and signed releases live on GitHub.
The documentation covers every setting, file path and modding detail, and the Discord is where you'll get an answer fastest. Download Chud for Windows — free, ~12 MB, no admin needed.