Open-source project
hicccc77/WeFlow avatar
hicccc77/WeFlow

WeFlow: a local WeChat history viewer and exporter that ships without its own decryption component

WeFlow - a local app for exporting WeChat chat history and generating annual reports.

16,069 stars887 forksUnknownNOASSERTION

At a glance

What is it?
WeFlow is an Electron desktop app that reads WeChat chat history locally, analyses it, exports it in formats from HTML to PGSQL and serves it over a localhost HTTP API. It depends on a native decryption component you have to supply yourself, and several of its features act on other people's messages.
Who is it for?
WeFlow fits WeChat users on Windows 10+ x64, Apple Silicon Macs or x64 Linux who want to keep and analyse their own chat history locally and can provide the native decryption component the app depends on. It does not fit Intel Mac owners, anyone who expects a working decryptor out of the box, or anyone uncomfortable with tools that block other people's message recalls and Moments deletions.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • hicccc77/WeFlow16,069 ★ · +1,649
Star history
Repository2026-09-222026-11-15
hicccc77/WeFlow14.4k16.1k

1,649 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A desktop app that reads WeChat data locally and in real time

WeFlow presents itself as a fully local, real-time tool for viewing, analysing and exporting WeChat chat history, and for generating data summaries and annual reports from it. The repository is an Electron application built with Vite: package.json sets dist-electron/main.js as the entry point, with an electron/ directory alongside src/, shared/, public/ and index.html. The current package version is 5.0.0.

Fully local is the core promise. Chat history stays on the machine where WeChat already stores it, and WeFlow reads it there rather than uploading it to a service. Real time means new messages show up as they arrive; a desktop notification feature pops up alerts for incoming messages and supports block and allow lists so you can limit which conversations trigger them.

The homepage is weflow.top, and there is a Telegram channel at t.me/weflow_cc.

The native decryption component is yours to build

The first thing to know before downloading anything: WeFlow depends on a custom native decryption component that is not part of the project. A tip at the top of the README says the app needs a matching third-party pluggable component, that the project relies on this custom native decryption component, and that you have to design it yourself. docs/third-party-components.md explains what it must provide.

The consequence is significant. Every feature that touches message content, from viewing chats to decrypting images to exporting history, sits behind that component. Someone who installs WeFlow expecting a finished tool will find the decryption step missing and will need either the skills to write a native module to the documented interface or a component from somewhere else, with all the trust questions that raises for code that reads private messages. The package scripts also include test:wcdb, which runs node --test scripts/check-wcdb-optional-exports.cjs.

Three platforms, one CPU architecture each, and no GitHub releases

WeFlow targets three desktop platforms, each with a single architecture. Windows needs Windows 10 or later on x64 and installs from an .exe; an installer.nsh script sits at the repository root. macOS support is Apple Silicon only (M series, arm64) via a .dmg. Linux support covers x64 (amd64) machines with an .AppImage or a .tar.gz.

That leaves gaps. Intel Macs, Windows on ARM and ARM Linux boards are not on the list, so owners of those machines have no package to install and would be building and testing on their own.

The repository also has no GitHub releases, even though the README carries a releases badge. The packages are not attached to tags on GitHub, so look to the weflow.top homepage for downloads or build from source. Without tagged releases there is no changelog per version on GitHub either; the last push to the repository was on 2026-10-28.

Export formats run from HTML and Markdown to PGSQL and ChatLab

Exporting is where WeFlow does the most. Chat history can be written out as JSON, HTML, Markdown, TXT, Excel, CSV, PGSQL and a ChatLab-specific format, among others. Contacts can be exported as lists of friends, group chats and official accounts. Moments content can be exported too, after the images, videos and Live photos in it are decrypted.

On the analysis side, private chat analysis counts messages between you and a friend, breaks them down by message type and sender ratio, and shows how messages are spread across times of day. Group chat analysis shows member details, a ranking of who talks most, active hours and the media posted. Annual reports summarise a single year, and a longer history report spans several years. A two-person report builds an analysis from your chats with one chosen friend.

The practical limit is that every one of these outputs is only as good as the decryption component behind it, and the formats are snapshots: an export does not stay in sync with later messages.

Some features act on other people's messages and posts

Several items in WeFlow's feature table go beyond archiving your own data. Anti-recall prevents messages sent by other people from being withdrawn. The Moments module intercepts deletion and hiding, so posts a friend removes or hides can remain visible to you. The contacts module can recover some former friends. In chats, WeFlow can modify local messages.

Each of these has a consequence. Anti-recall and Moments interception keep content that its author chose to take back, which raises privacy questions for the people on the other side of the conversation and, depending on where you live, legal ones. Editing local messages means an exported history is not proof of what was actually sent, so do not treat WeFlow exports as an untouched record in a dispute.

The README closes by asking users to use the tool responsibly and comply with relevant laws and regulations. Whether a given feature is lawful where you live is your call to make before you switch it on.

A localhost HTTP API on port 5031

WeFlow can expose its local message data through an HTTP API so other tools and scripts can query it. The service is off until you turn it on under Settings, then API service, then Start service. It listens on port 5031 by default, at the address http://127.0.0.1:5031, and returns either raw JSON or the ChatLab standard format. The full interface is in docs/HTTP-API.md.

The feature table describes this as mapping local message capabilities onto HTTP so you can connect external systems, automation scripts and further development. That is useful for anyone who wants to search or post-process chat history from their own code.

It also widens the exposure. Binding to 127.0.0.1 keeps the service off the network, but any program running on the same machine can send requests to that port. On a shared computer, or one running software you do not fully trust, read docs/HTTP-API.md for how requests are authorised before starting the service, and stop it when you are not using it.

Building from source runs a postinstall chain before anything starts

The developer steps are short:

bash
git clone https://github.com/hicccc77/WeFlow.git
cd WeFlow
npm install
npm run dev

More happens under npm install than the four lines suggest. The postinstall script runs patch-package, then electron-builder install-app-deps, then node scripts/prepare-electron-runtime.cjs. A failure in any of those three steps fails the install, and a separate rebuild script calls electron-rebuild. The dev script runs the same runtime preparation before starting Vite.

A full build is stricter. npm run build type-checks both the renderer and the Electron code with tsc against tsconfig.json and tsconfig.node.json, cleans dist-electron, runs vite build and then electron-builder. A type error anywhere stops the build.

The dependency list also includes the ai package and @ai-sdk providers for Anthropic, Google, OpenAI and OpenAI-compatible endpoints. If a feature sends chat text to a hosted model, that text leaves your machine, so check which provider is configured before using it.

No license identifier, and forks are asked to keep the author fields

GitHub reports the license as NOASSERTION, meaning it could not match the LICENSE file to a standard license identifier. The primary language is not detected either. If you plan to fork, redistribute or embed WeFlow, read LICENSE yourself rather than assuming any particular open-source terms.

package.json carries a comment aimed at forks: modified versions should not change the author and application information in that file. The author is listed as cc with the address [email protected], the same address the README gives for promotion, cooperation and advertising enquiries. The partners section of the README is still a placeholder.

The dependency on @vscode/sudo-prompt is worth noticing for anyone auditing the app before installing it on a work machine, since that package exists to request elevated privileges. Check when WeFlow asks for administrator rights and what it does with them.

Editorial conclusion

WeFlow fits WeChat users on Windows 10+ x64, Apple Silicon Macs or x64 Linux who want to keep and analyse their own chat history locally and can provide the native decryption component the app depends on. It does not fit Intel Mac owners, anyone who expects a working decryptor out of the box, or anyone uncomfortable with tools that block other people's message recalls and Moments deletions. Before installing, read docs/third-party-components.md, check the LICENSE file yourself because GitHub reports NOASSERTION, and decide whether you will enable the HTTP API at all.

Frequently asked questions

What is WeFlow?

WeFlow (hicccc77/WeFlow) is a fully local desktop app for viewing, analysing and exporting WeChat chat history and generating annual reports from it. It runs on Windows 10+ x64, Apple Silicon Macs and x64 Linux.

Does WeFlow include the WeChat decryption component?

No. WeFlow depends on a custom native decryption component that you have to design yourself; docs/third-party-components.md describes it.

Does WeFlow run on Intel Macs?

WeFlow lists macOS support for Apple Silicon (M series, arm64) only, packaged as a .dmg. Intel Macs are not among the supported devices.

What port does the WeFlow HTTP API use?

Port 5031 by default, at http://127.0.0.1:5031. Enable it under Settings, API service, Start service; it returns raw JSON or ChatLab format.

Official sources

  1. hicccc77/WeFlow on GitHub
  2. Issues
  3. Project website
  4. README
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/hicccc77-weflow.svg)](https://hysenlabs.com/projects/hicccc77-weflow)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/hicccc77-weflow.svg)](https://hysenlabs.com/projects/hicccc77-weflow)

Was this useful?