Project
Credits
Zapret2UI is a shell. Almost everything here that actually does the work was invented and written by other people, and here is exactly who.
This is not a formality: each entry says what specifically came from there, so you can see what the program is made of and where to go for the original.
The bypass engine
bol-van / zapret2
winws2 itself: packet interception, every desync technique, the Lua libraries, the
orchestrators, the ready-made blobs with client hellos. Everything described in
How it works and the Reference is a
capability of that engine.
Zapret2UI contains no bypass logic of its own at all. It assembles a command line, starts a process and shows the result. Without that project this program would simply not exist.
The official engine manual remains the primary source for any verb or parameter.
The same author also made the original zapret, which most builds and guides grew around. How the two generations differ is explained here.
Strategies
Flowseal / zapret-discord-youtube
A set of working configurations that the community field-tested against live providers for years. More than half of Zapret2UI's built-in set are translations of those onto the second-generation engine: ALT10, ALT11, the multisplit with seqovl variant and the fake plus fakedsplit combination.
The same source gave us approaches that are far from obvious on their own: picking the overlap values, domestic blobs for the fakes, and the "only bypass what is on the lists" mode.
Telegram proxy
Flowseal / tg-ws-proxy
The idea and the working path of the built-in proxy: MTProto over WebSocket, resolving through DoH and fronting through domains behind Cloudflare, including the front pool that benches the ones that fail.
The original is written in Python and ships as a separate program. Here the protocol has been rewritten in C# and built into the application, so there is no second process and no Python runtime to carry. The working logic is kept as it was.
The idea of a shell
RaccoonLaptop / ZapretUI
The project that started the thought that the engine deserves a proper graphical interface rather than a pile of .bat files. Zapret2UI is written from scratch and for a different engine, but the starting point came from there.
The DPI check method
hyperion-cs / dpi-checkers
A way to detect a volume limit: the connection is established, the first few dozen kilobytes get through, and then the stream stalls. A short handshake never hits such a limit, so an ordinary check reports "clean" and a separate test with a large download is required.
That method powers the "DPI check" button. Licensed under Apache 2.0.
Fonts and libraries
The program's interface and this site share the same typography.
| What | Where it is used | Licence |
|---|---|---|
| Hanken Grotesk | Body text in the interface and on the site. | SIL Open Font License |
| Space Grotesk | Headings. | SIL Open Font License |
| JetBrains Mono | Command lines, the journal, strategy arguments. | SIL Open Font License |
| Emoji.Wpf | Colour emoji in the program's interface. The only external dependency of the build. | see the repository |
The program itself is written in .NET 9 and WPF. There are no other third-party packages in the build: everything else, including the proxy, the diagnostics and the networking, is done with the standard library.
The community
Special thanks to everyone who writes in the channel and files issues in the repository. There are many providers, their equipment differs, and there is no way to test all of it alone. Almost every change to the set of built-in strategies came out of someone reporting what worked and what did not.
If something unusual started working for you, say so: which provider, which city and which strategy. How that helps and what else you can do: Support.
Licences
- Zapret2UI is distributed under the MIT licence. The source is open; you are free to use and modify it.
- winws2 ships under its own licence, see the zapret2 repository.
- dpi-checkers is under Apache 2.0, the fonts are under the SIL Open Font License.
The program is not affiliated with Discord, YouTube, Google, Telegram or VK. The names and client hellos of their services are used only as the contents of fake packets — that is, technically — and imply no association with those companies.