Vencord: what the client mod changes and what it cannot do
The cutest Discord modification
At a glance
- What is it?
- Vencord injects into the Discord desktop and browser client to add 100+ built in plugins, a CSS theme editor and blocked analytics, and the project itself says client modifications break Discord's terms of service. Worth reading the install path and the two defaults it changes before you touch an account you care about.
- Who is it for?
- Adopt Vencord if you want plugin control and theme editing on a Discord account you can afford to lose, and do not adopt it for a work or primary account, because the project itself says client mods violate the terms of service and can end with a disabled account.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Vendicated/Vencord14,522 ★ · +388
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| Vendicated/Vencord | 14.1k | 14.5k |
388 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A mod that layers on the Discord client, not a replacement for it
Discord stays installed and stays signed in. Vencord injects into the client, which is why every line in the project's feature list is phrased as something running on top of what you already have: it works on any Discord branch, Stable, Canary or PTB, and it ships 100+ built in plugins. For a user that means one download and one injection step rather than a parallel chat application to migrate to.
What pulls people in is the plugin catalogue and the CSS editor, which between them replace a separate theming tool plus hand written stylesheets. What makes an engineering team hesitate sits in the same file, in a section collapsed behind a summary tag.
The licence is GPL-3.0-or-later, which matters if you plan to publish your own build or redistribute a patched one, because derivative distributions carry the same obligation. Nothing in the repository grants a different exception. The disclaimer in the README covers trademark only: Discord is named for descriptivity, with no affiliation and no endorsement.
A pnpm workspace where the browser target is built separately
src/ holds the desktop mod, browser/ the web target, packages/ shared code and generated type declarations, patches/ the applied patches, and pnpm-workspace.yaml marks the whole tree as a pnpm workspace. Nothing at the top level is a published library. package.json sets private to true, so there is no registry package to depend on, and consumers install a build rather than a dependency.
Contributors clone and build locally. Four script entries do the work that matters, and they are declared in package.json rather than explained in prose:
"buildWeb": "node --require=./scripts/suppressExperimentalWarnings.js scripts/build/buildWeb.mjs",
"inject": "node scripts/runInstaller.mjs -- --install",
"uninject": "node scripts/runInstaller.mjs -- --uninstall",
"generateTypes": "tspc --emitDeclarationOnly --declaration --outDir packages/vencord-types --allowJs false"The buildWeb script is the browser target, with --standalone and --reporter passed through by the variant scripts beside it. inject and uninject are the install and uninstall paths, both routing through scripts/runInstaller.mjs, so those two flags are the whole maintainer side of installation. generateTypes writes declarations into packages/vencord-types with tspc, which is the reason that directory exists in the layout at all.
For a reader, the practical consequence is that a clone gives you a build tree rather than a product. Nothing in this script list produces a signed or checksummed artifact, and these commands assume a working Node and pnpm toolchain on your own machine.
One 2022 devbuild in the release feed, and 1.15.9 in package.json
Version 1.15.15 is a field inside package.json, not a tag you can resolve. The repository's release list holds a single entry, devbuild (DevBuild 8d64c8b), dated 2022-10-27, while the last push to the default branch was on 2026-11-01. Read those two facts side by side and the picture is unambiguous: work continues on main, but it does not surface as tagged releases.
That has direct consequences for how you adopt this. You cannot pin a known good build from a version list, and you cannot diff two versions from the release feed.
The README routes installation to https://vencord.dev/download, while the homepage field in package.json still points back at the GitHub readme. Small inconsistency, but it tells you where the canonical build host is. If your process needs a reproducible artifact with a checksum, this repository does not supply one, and the README does not document how a build is verified or signed before you run it.
The install path is one URL, and the browser has two delivery routes
The entire installation procedure in the README is one sentence and one address: visit https://vencord.dev/download. There is no command line installer for end users in the documentation, and one should not be invented for it.
On the browser, two routes exist, both named in the feature list: a browser extension, or a UserScript. The UserScript route is the practical one where you cannot or will not install an extension, since it lives in a script manager you already control. On desktop, the page decides what you receive, and the README does not enumerate per platform files or versions.
Uninstalling works by symmetry rather than by a documented key: whatever platform you installed on owns the reverse operation, and the maintainer side of the same action is the uninject script shown above.
The gaps matter as much as the steps. The README documents no Android or iOS build, and it does not say which browsers the extension target supports or which extension manifest version it expects. Someone on a phone, or on a managed browser that blocks extensions, has no documented path here. The support server linked in the README, https://discord.gg/D9uwnFnqmd, is the only escalation route the project names.
Analytics and crash reporting are blocked, so the client fails quietly
Two defaults run against the host application. Discord analytics and crash reporting are blocked out of the box, and the project states it carries no telemetry of its own.
For a privacy minded user that is the right trade. For an engineer debugging a broken client it removes the one channel that would have told you what went wrong. When a plugin throws and the client wedges, the crash report never leaves the machine. The README does not document how to re-enable reporting or what the setting is called, so the remaining signals are the browser console and the support server.
The no telemetry claim is also stated rather than demonstrated. No audit reference or network capture is offered in the README, so a policy that requires evidence instead of a sentence leaves that judgement to you. The same caution applies to the privacy framing in general: blocked analytics are a client side default, and the client is the layer the project controls, not the server.
The CSS editor imports BetterDiscord themes, and that is the whole migration story
Themes are where the clearest path in from elsewhere lies. The client has an inbuilt CSS editor with an importer that accepts any css file, BetterDiscord themes included, so a theme you already run can be brought across by importing the file rather than by installing a second application. That is the difference in approach worth naming: editing happens inside the client you are already running, instead of in a separate theming host that has to exist first.
The importer's contract is file level, not compatibility level. A theme that depends on variables or class names Discord defines in its own way is not covered by the word import, and nothing in the README or the repository lists themes known to break. If a theme renders wrongly after import, the diagnostic work is yours. The plugin list linked from the README explains what plugins do, not which selector your stylesheet is fighting.
Custom CSS is also the sharpest edge in the whole project. You are injecting rules into someone else's application, and Discord ships markup changes without asking you. When a client update makes your stylesheet cover the composer, the rollback is deleting the CSS you wrote, not filing an issue anyone can reproduce.
The disclaimer admits the terms of service violation and hands you the risk
Client modifications are against Discord's terms of service. The project says so in a collapsed section, then adds that Discord is indifferent, that there are no known cases of users getting banned for client mods, and that all inbuilt plugins are safe to use. Take the three claims separately. The first is a fact about the contract. The second is an absence of reports, which is not permission, and it is a claim about enforcement you cannot check from outside. The third is scoped to built in plugins, so it does not cover what you import or what you write yourself.
The project's own advice for a high stakes account is the clearest sentence in the file: if your account being disabled would be a disaster, do not use any client mods, and not just this one. It also tells you not to post screenshots with Vencord visible in a server where that could get you removed, which turns a modding decision into a habit you have to police in every server you join.
On upkeep, the repository is not archived and the last push was on 2026-11-01. The project claims broken plugins are usually fixed within 12 hours. Read that claim narrowly, because it is about plugin code and not about the client: Discord ships changes that a patch has to follow, and a 12 hour figure says nothing about how fast a rebuilt package reaches the download page or your machine.
Editorial conclusion
Adopt Vencord if you want plugin control and theme editing on a Discord account you can afford to lose, and do not adopt it for a work or primary account, because the project itself says client mods violate the terms of service and can end with a disabled account. Before installing, check two things the documentation does not settle: the version your download page hands you cannot be pinned against a release feed that still shows a 2022 devbuild, and the crash reporting Vencord blocks is the signal you would have used to diagnose a broken client.
Frequently asked questions
Can I get banned for using Vencord?
Client modifications are against Discord's terms of service, which the project states directly. It also states there are no known cases of users getting banned for client mods, and advises skipping client mods entirely if your account being disabled would be a disaster for you.
What is Vencord for?
Vencord modifies the Discord client to add 100+ built in plugins, an inbuilt CSS theme editor, blocked analytics and crash reporting, and optional settings sync. It works on the Stable, Canary and PTB branches and also runs in a browser through an extension or a UserScript.
How do I install Vencord?
The documented install step is a single instruction: visit https://vencord.dev/download. No command line installer is given for end users, and the inject and uninject scripts in package.json exist for contributors building from a clone.
How do I use Vencord themes?
Themes are edited in the inbuilt CSS editor, which can import any css file including BetterDiscord themes. The README does not list which themes are known to be incompatible after import.
How do I use the Vencord extension in a browser?
Browser support works through either a browser extension or a UserScript. The README does not enumerate which browsers are supported, so check the download page for the target you need before assuming an extension build exists for it.
Is Vencord better than Discord?
Vencord modifies the Discord client rather than replacing it, so Discord still does the work and Vencord layers plugins and theming on top. The README makes no quality comparison between the two.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vendicated-vencord)Star history chart for your README
[](https://hysenlabs.com/projects/vendicated-vencord)Was this useful?