A 17NAS account is created automatically on first sign-in
Tools
WeChat Chat Simulator
Build a chat conversation with the structured editor or DSL text: custom nicknames, avatars, status bar and six message types, with live preview and PNG export. Output is a mockup rendering, processed entirely in your browser.
⚠️ Mockup notice: this tool is for interface demos, prototyping and content creation only. Generated content does not represent real chat records and must not be used to impersonate, fabricate evidence, defraud, spread rumors or mislead. Everything is processed locally and cleared on refresh.
基本信息
对话内容
Add message
One message per line: A said: text (contact) | B said: text (me) | Time: xx | A said: [Red packet: text] | B said: [Image: 1] | A said: [Voice: 12] | System: notice. Click "Apply to editor" to parse.
Live preview
Exports a 2x-resolution PNG identical to the preview.
🔒 Privacy: conversations, avatars and images are processed entirely in your browser — nothing touches a server, no copies are kept, everything is destroyed on refresh.
How to use
Set the contact nickname, both avatars (optional local upload, ≤2MB) and the status bar under "Status bar & identity"; without an upload, a locally generated colored avatar is used.
Add messages one by one in "Card editor": text, time, red packet, voice, image, system — with sender switching and reordering; the preview refreshes live.
For batch work, switch to "DSL text mode": one message per line (A=contact, B=me), supporting [Red packet: text], [Image: n] and [Voice: seconds] syntax; "Apply to editor" parses and fills the cards.
Click "Export PNG" to save a 2x-resolution chat image identical to the preview. Please use the generated content in compliant scenarios.
常见问题
Which message types are supported?
Six types are supported: text, time separators, red packets, voice (width scales with seconds), images (local upload, referenced by number) and system notices (recall, red-packet received, etc.). Transfers and stickers are on the roadmap.
Are generated screenshots stored on a server?
No. All rendering and export happen locally in your browser. Conversations, avatars and uploaded images never reach any server and are destroyed on refresh. The exported PNG only lives on your own device.
DSL text mode vs card editor?
Both edit the same data: cards suit per-item tweaks (type, sender, reordering), DSL suits batch pasting or quick rewrites. "Apply to editor" parses the whole text and refills the cards; unrecognized lines are reported with line numbers.
What format and resolution is the exported image?
Exports a 2x-resolution PNG (about 750px wide) identical to the preview — great for sharing in chats, embedding in documents or posting on social media. The editing-time notice is not included in the export.
Any limits on avatars and images?
Avatars: JPG/PNG/WebP under 2MB; chat images under 5MB. Files stay in browser memory as Base64 for rendering only — never uploaded or persisted. Without an upload, colored letter avatars are generated locally.
What is the compliance boundary of this tool?
Allowed: interface demos, product prototypes, content creation, teaching examples — any setting where the audience can clearly tell it is a mockup. Forbidden: impersonation, fabricating chat evidence, fraud, rumors or misleading material. Exports carry a mockup mark; removing it to share violates the terms here and may violate the law.
Will more message types (transfers, stickers, group chat) come?
On the roadmap: transfer cards, sticker messages, multi-participant group chat, more status-bar styles. The DSL syntax will stay backward compatible — text-mode content you have now keeps working in future versions.
