picacg-qt: a Qt6 desktop client for the PicACG comic service

What picacg-qt is for, and who it is written for

PicACG is a comic service, and picacg-qt is one of several desktop clients for it. The README describes the project as a PC client for the service on Windows, Linux and macOS, with a Qt interface, and states that it implements most of the service's features, with viewing and downloading called out explicitly. The stated scope is narrow: the README says the project is for technical research and asks users not to put it to other uses. Treat that line as part of the project's self-description rather than as legal advice.

The audience is a reader who wants a desktop application rather than a browser tab or a phone. The repository ships a translate directory and a ui directory alongside src, which is what you would expect from a PySide6 application that carries localized strings and Qt Designer files. The topics list mentions bika, picacg, picacomic, doujinshi and r18, so the content the client is built around is adult-oriented.

This is not a general comic manager. It does not aggregate sources, it does not maintain a library format of its own, and the README does not describe any plugin interface. If you want one client per service, picacg-qt is one of them.

The PySide6 and Qt6 structure behind the client

The primary language is Python and the badges require Python 3.10 or later. The interface layer is Qt, and the topics name both pyside6 and qt6. The repository layout backs that up: src holds the application code, ui holds the Qt interface definitions, translate holds localization files, and res holds resources. A script directory contains build_qrc.py, which the README says generates the qrc resource file, and a separate script/build_qrc.py step is listed under the GitHub Actions build instructions.

The README credits several upstream projects by name. waifu2x, waifu2x-ncnn-vulkan and tonquer's own waifu2x-vulkan are listed under the upscaling feature, and the Qt material comes from PyQt5/PyQt, PyQt5/PyQtClient, qt-material for the skin, QSS-Skin-Builder, and Groove for smooth scrolling. That credit list is the clearest statement of the architecture in the README: the client is a Qt shell around a service API, with an optional Vulkan-backed upscaler attached.

What the README does not describe is the network layer. There is no mention of how requests are authenticated beyond the login screen shown among the example images, no rate-limit discussion, and no statement about what happens when the service changes its endpoints. That silence is the main architectural risk for anyone building on top of the code rather than just running it.

Installing picacg-qt on Windows, macOS and Linux

The README does not describe a source install. It points at the releases page and gives per-platform steps for prebuilt archives. On Windows, the README says to download the latest release, unzip it, and open start.exe; later updates are handled by downloading the newest version over the existing directory. The README notes the Windows build was tested on Windows 10.

If waifu2x fails to initialize with a DLL error, the README points at two runtime installers rather than at a code fix: the Visual C++ redistributable and the Vulkan runtime.

# Windows: only if waifu2x initialization fails with a DLL error
# install the VC++ redistributable and the Vulkan runtime linked in the README

On macOS, the README says the archive is a 7z file, that you should drag the extracted PicACG into the Applications folder in Finder, and that you launch it from Launchpad. The tested version listed is macOS 10.15.7.

On Linux, the README gives an explicit sequence. It tests on deepin 20.2 and starts with a Debian package for libxcb-util1, then the release tarball.

sudo dpkg -i ./libxcb-util1_0.4.0-1+b1_amd64.deb
tar -zxvf bika.tar.gz
cd bika && chmod +x start
./start

The README adds that waifu2x on Linux requires a device that supports Vulkan and the mesa-vulkan-drivers package.

sudo apt install mesa-vulkan-drivers

For proxy configuration, the README does not document a setting. It redirects to issue tonquer#48, which is worth reading before you assume the client will work on a restricted network.

waifu2x upscaling and its Vulkan dependency

The upscaling path is the feature that separates picacg-qt from a plain reader, and it is also the part most likely to break. The README lists waifu2x as a feature and includes a waifu2x.gif among the example images, but the only troubleshooting it offers is the DLL error on Windows and the Vulkan driver note on Linux. There is no CPU fallback documented, no quality preset table, and no statement about how much VRAM the upscaler needs.

That matters because Vulkan support is uneven. On Linux the README asks for mesa-vulkan-drivers, which covers the common Mesa drivers but says nothing about proprietary drivers or older integrated GPUs. On macOS the README does not mention Vulkan at all, and the platform has no native Vulkan driver, so the status of waifu2x on that platform is not something the README settles. If upscaling is the reason you are interested, verify it on your own machine before committing.

The repository topics also name realcugan and realesrgan alongside waifu2x, which suggests the upscaling feature is not limited to a single model family, but the README does not document model selection or where model files live. The example directory contains only images and GIFs, so there is nothing in the repository to confirm how models are shipped or fetched.

Where picacg-qt is the wrong tool

The clearest limitation is scope. picacg-qt talks to PicACG. If the service is unavailable in your region, or you want a client that reads from several sources, this project does not help, and the README offers no alternative endpoint configuration. The proxy question is deferred to a single issue thread rather than documented in the README.

A second limitation is the interface. Everything described is GUI: login, search, comic detail, download, viewer, waifu2x. The README does not document a command-line mode or a headless downloader, so scheduling downloads on a server is not a supported path as far as the documentation goes. If you need that, you are writing your own client against the service API.

A third is the packaging model. Updates on Windows are handled by extracting a new archive over the old directory, which the README states directly. There is no package-manager recipe in the README, and the Linux instructions start from a tarball and a manually installed Debian package. On a managed fleet, that is manual work every release. The CHANGELOG file exists at the top level, so release notes are available, but the README does not describe a rollback procedure, and the archive-overwrite update style makes rollback a matter of keeping the previous directory.

How picacg-qt compares with EhViewer and other clients

The related searches around this project include EhViewer, which is the natural comparison point for anyone looking at desktop and mobile comic clients. The difference in approach is the service and the platform target. EhViewer is associated with a different site and a different client lineage; picacg-qt is written specifically against PicACG and ships as a Qt desktop application for Windows, macOS and Linux. If your library lives on the other service, picacg-qt is not a substitute, and the README does not claim to support multiple backends.

The same author maintains JMComic-qt and ehentai-qt, both listed at the bottom of the README. That is a more useful comparison than any external tool: the three projects share a shape, one Qt client per service, and the README presents them as a family. If you have used one, the interaction model will be familiar, and the trade-offs around Vulkan-based upscaling and archive updates are likely to be similar. The README does not state whether the three share code, so treat that as an open question rather than an assumption.

Against a browser, the case for picacg-qt is offline reading and the download manager. Against a generic downloader, the case is the integrated viewer. Neither argument survives if you need automation.

Licence and maintenance cost

picacg-qt is licensed under LGPL-3.0, and the repository carries a LICENSE file at the top level. The LGPL matters if you intend to link the code into another application or redistribute a modified build: the licence family carries obligations around source availability and relinking that the GPL does not phrase the same way. The README does not discuss the licence beyond the badge, so read LICENSE.txt yourself and get proper advice if you plan to redistribute. Nothing here is legal advice.

The maintenance picture is active. The last push to the main branch was on 2026-09-22, and the most recent release, v1.5.5, was published on 2026-09-06. Before that, v1.5.4 came out on 2026-02-28 and v1.5.3 on 2025-11-01. The cadence is uneven: roughly four months between the November and February releases, then about six months to v1.5.5. A client like this inherits breakage whenever the upstream service changes, so the gap between releases is the interval during which a service-side change can leave the client broken.

Upgrade cost is low for end users, since the README's Windows path is overwrite-in-place and the Linux path is re-extract and rerun start. The build path is heavier: the README's compilation instructions route through GitHub Actions and begin with running script/build_qrc.py to generate the qrc file, so anyone building from source should expect to work through the workflow definitions in .github rather than a documented local build command.

Editorial conclusion

Adopt picacg-qt if you want a native desktop reader for PicACG on Windows, macOS or Linux and you are willing to install the VS and Vulkan runtimes it depends on. Skip it if you need a documented CLI, a headless downloader, or a client for a service other than PicACG. Before you rely on it, open a release archive, run the start binary, and confirm whether waifu2x initializes on your GPU; the README treats that step as the common failure point and points at the runtime installers rather than at a fallback.

Frequently asked questions

Official sources

1. Issues
2. License: LGPL-3.0
3. README
4. Releases
5. tonquer/picacg-qt on GitHub