ComfyUI-DD-Translation: keeping the ComfyUI front end readable in Chinese

A fork that exists because the original stopped and ComfyUI moved on

ComfyUI-DD-Translation is a derivative branch of AIGODLIKE-ComfyUI-Translation, and the project credits the original developers for their work on the open source community. The reason for the fork is stated plainly in the background section: the original author stopped updating, ComfyUI's own Chinese support has progressed slowly, and in particular the adaptation for custom nodes lagged. The fork's stated goals follow from that, to be compatible with the latest ComfyUI version, to add new translation content, and to improve the translation experience.

That framing explains the whole shape of the project. It is not a general internationalisation effort. The scope is explicitly Simplified Chinese, and the reason given is a personal limit on the maintainer's time. The project says it does not consider multilingual support for now.

The architecture of the fork is visible in the repository listing. There is an __init__.py for the ComfyUI custom node entry point, a js/ directory for the front end part, a zh-CN/ directory holding the translation content, a config.json in the root, a standalone translation generator page in the root, and a pyproject.toml that packages it for the Comfy Registry.

The pyproject metadata is minimal and tells you how the plugin is distributed.

[project]
name = "ComfyUI-DD-Translation"
description = "A translation branch project."
version = "2.1.1"
license = "LICENSE"

It also carries the Comfy Registry fields, with a PublisherId of Dontdrunk and a DisplayName of ComfyUI-DD-Translation, and a dependency that points at a branch of this same repository, which is how the translation content is pulled in.

The audience is a Chinese speaking ComfyUI user, and the primary language of the repository is recorded as HTML, which reflects that the bulk of the work is front end string files rather than Python.

Two translation sources, and a switch between them

The feature list describes a design decision that is easy to miss. The plugin does not replace ComfyUI's official Chinese localisation, it layers on top of it. The project says it embeds extra translation content on the basis of the official Chinese version, to achieve more complete translation, and the interface provides a convenient toggle button to choose between the additional translation and the official implementation.

Using the official implementation means switching the plugin off, so that the plugin has no effect and ComfyUI's own already-translated Chinese content is used instead. That is an unusually honest arrangement, and it tells you something about the project's expected lifespan: the maintainer expects the official translation to keep improving and to eventually cover most of what the plugin adds.

The button is a draggable floating component, added in version 2.2.0, described as a UI component update along with a new setting that turns the front end UI component on or off, enabled by default.

Two other front end details come from the same changelog. Version 2.1.1 fixed a case where typing terms such as free or cfg into the search box froze the interface, and it restored a tooltips key translation logic that had gone missing, so that all node tooltips now have Chinese translations. Version 2.0.0 changed how the translation is toggled, moving it to ComfyUI's own settings panel and removing the faulty translation files that were causing bugs.

The deeper architectural change came in version 1.9.0, described as a functional refactor. All remaining browser translation cache mechanisms were removed, and from then on the plugin's communication happens entirely through dynamic interaction with the backend API. A configuration json file was added at the root so that cloud users can control whether translation is on.

That is the piece worth understanding if you operate ComfyUI remotely. Before 1.9.0 the plugin relied on browser-side caching of translations, and after it the translation content is fetched dynamically.

Installation is a folder copy, a git clone or a Manager search

Three installation methods are documented, and the last two are marked as recommended.

The first is manual. Download the project, put the whole folder into the custom_nodes directory of ComfyUI, and restart ComfyUI.

The second is to install with git from Manager or from a launcher, using this URL.

https://github.com/Dontdrunk/ComfyUI-DD-Translation.git

The third is the simplest: search for the plugin by name in Manager and install it. Since ComfyUI-Manager is the standard way most users handle custom nodes, that path is the one a new user will take, and it is the one the project recommends.

There is one hard requirement that is easy to miss. The documentation states that this project is not compatible with the older translation plugin AIGODLIKE/AIGODLIKE-ComfyUI-Translation, and that the old plugin must be uninstalled before installing the new one. Two translation plugins both rewriting the same front end strings is exactly the kind of conflict that produces garbled labels, so this is a sensible instruction rather than a technicality.

The project also states which user it is aimed at. It mainly targets users on the latest ComfyUI version, it prioritises support for the newest ComfyUI, and it may drop compatibility with older versions. The recommended setup is an all-in-one package updated within the last six months, or the official desktop version, and users of an all-in-one package are advised to use Chrome or Edge to ensure the best front end compatibility.

Translation problems are collected through a dedicated issue page rather than the general tracker, which is a reasonable way to keep a large number of string reports in one place.

The custom node translation list is the real content of the project

What the plugin actually contributes is a long list of translations for third party custom nodes, and the changelog is a ledger of that work. The pattern across versions is consistent: a named contributor submits translations for a set of plugins, and the maintainer merges them into the release.

Version 2.2.3 in May 2026 merged a large batch of plugin translation completions from one contributor. Version 2.2.2 in March 2026 merged three plugins: Comfyui-ZiT-Lora-loader, ComfyUI-ZImagePowerNodes and ComfyUI-EditUtils. Version 2.2.1 in January 2026 completed the ComfyUI-Qwen-TTS plugin translations.

Earlier releases show the same cadence with a longer tail. Version 1.8.10 brought in a group of plugins including ComfyUI-VideoHelperSuite, comfyui-reactor-node, comfyui-mixlab-nodes, ComfyUI-LivePortraitKJ, ComfyUI-InstantID and ComfyUI-Inpaint-CropAndStitch, alongside a longer list of plugins whose translations were completed.

The coverage spans the usual ComfyUI ecosystem: rgthree-comfy, ComfyUI-Manager, WAS Node Suite, ComfyUI_IPAdapter_plus, ComfyUI-ControlNet_aux, ComfyUI-KJNodes, ComfyUI-Easy-Use, ComfyUI-Advanced-ControlNet, ComfyUI-VideoHelperSuite, ComfyUI-MimicMotionWrapper, and video and audio tooling such as ComfyUI-WanVideoWrapper, SeedVR2_VideoUpscaler, TTS2-series plugins, IndexTTS2, EdgeTTS and CosyVoice.

Two entries in the changelog show the maintainer making judgement calls rather than translating everything. Version 1.8.11 deleted the translation files for RMBG and LayerStyle, because those plugins ship their own Chinese and about ninety percent of their content is already localised, with the remaining dropdown items to be added later. Version 2.0.1 removed the ComfyUI template translation files entirely, on the grounds that ComfyUI's official translations have gradually implemented complete Chinese template translation.

That is a good sign of a maintainer watching what upstream does, and it is also the clearest statement of the plugin's remaining value: it covers what the official translation does not, mainly the node panels of third party extensions.

Version 2.1.0 dropped legacy interface support to fix performance problems

One changelog entry matters more than the string merges, because it changes who can install the plugin.

Version 2.1.0, dated 2025-12-10, removed the compatibility code for the old ComfyUI interface, and the plugin is no longer compatible with the older ComfyUI interface. The stated reason is that this solves a lot of performance problems. The documentation adds that if you need compatibility with the old ComfyUI interface, use a version before v2.0.0.

So the plugin made a deliberate choice: narrow the supported range, drop the legacy front end, and gain back responsiveness on recent builds. Anyone still on an old ComfyUI is expected to stay on an old plugin release, and the project warns at the top of the usage notes that it is not compatible with the AIGODLIKE plugin and that old versions may be dropped.

The 2.0.0 release, dated 2025-12-08 and labelled a compatibility update, is the other structural milestone. It added full translation support for the VUE NODES 2.0 node system and adapted comprehensively to the new node system in the latest version, fixed translations for node inputs whose labels include a leading character that had broken the lookup, and fixed a connection anomaly in the ComfyUI Nodes 2.0 nodes using a compatibility example contributed by one of the translators. It also switched the translation toggle to ComfyUI's native settings panel.

The overall pattern across the project history is a chase. Each ComfyUI front end rework forces a large translation pass, and the plugin absorbs that work so that users on current builds do not have to. That is a service, and it is also a treadmill, since the next ComfyUI rework starts the cycle again.

Where ComfyUI-DD-Translation is the wrong tool

The first wrong-tool case is a user who needs more than one language. The project is explicit that multilingual support is not considered, because the maintainer's personal capacity is limited, so it translates to Chinese only. A user working in an English interface with occasional Chinese documentation, or a team with several language requirements, gets no benefit.

The second case is a user on an old ComfyUI build. From version 2.1.0 the plugin no longer supports the legacy interface, and the project says it may drop older version support entirely, recommending a recent package or the official desktop version instead. An old installation is out of scope by design.

The third case is a user whose custom nodes are already covered by ComfyUI's own translation, or whose plugins ship their own Chinese. The changelog itself records the deletions for RMBG and LayerStyle on exactly that reasoning, and the template translations were removed in 2.0.1 for the same reason. Installing a third party translation layer on top of an already-translated front end adds a maintenance surface for no visible gain.

There is also a structural point about the upstream dependency. The plugin's value is entirely a function of how far ComfyUI's official Chinese support has advanced, and that gap moves in one direction, toward closure. A maintainer who keeps up with the front end rework is doing necessary work, and a maintainer who does not leaves users with half translated panels.

On licensing, the repository carries no classified licence, the licence field in the pyproject points at a file called LICENSE that is not in the top level listing, and the project was built on top of another open source project by a different author. A fork that inherits translations from an upstream project should have its licence position settled before anyone builds a business workflow on it, and the documentation does not address that.

Editorial conclusion

ComfyUI-DD-Translation suits a ComfyUI user on a recent release who reads Chinese and works with a set of custom nodes the official translation still leaves in English, and the two-minute install through ComfyUI-Manager is the cheapest way to try it. It does not suit a user who needs multiple languages, since the project states multilingual support is out of scope, and it does not suit someone staying on an old ComfyUI build, because version 2.1.0 removed the legacy interface compatibility. Before adopting, uninstall AIGODLIKE-ComfyUI-Translation as the documentation insists, since the two are not compatible, and switch the translation off through the toggle to see how much ComfyUI itself now translates before you add anything.

Frequently asked questions

Official sources

1. Dontdrunk/ComfyUI-DD-Translation on GitHub
2. Issues
3. README