Turn a WhatsApp chat export (.txt, or .zip with media) into clean dated Markdown for Obsidian, Logseq, legal archives or long-term backup. Reads both iPhone and Android formats, groups by date, lists attached media — entirely in your browser, your conversations never uploaded.
Detailed side-by-side format architecture for TXT Document (.txt) and Markdown Document (.md). Every conversion executes strictly within isolated browser memory without network transit.
Drag and drop your .txt file onto the working surface or use the system file dialog. File magic bytes are verified locally on device.
Select a quality preset (Lossless, Visually Lossless, Balanced, Smallest) or adjust advanced encoding switches in the options panel.
Click CONVERT to execute local WebAssembly compilation. Save the finished .md directly to local storage, or stage it for chaining.
Prefer local shell scripting? Run this standard POSIX command on your machine to achieve equivalent transcoding without a web interface:
# Convert TXT to MD locally
pandoc input.txt -o output.mdWorking with files across multiple web pages? The official convrtr Chrome Extension adds native Side Panel docking, right-click context menu media extraction, and visible viewport capture. Powered by the same zero-upload client-side WebAssembly engine.
Open the chat, tap the contact or group name, choose Export Chat, then Without Media (.txt) or With Media (.zip). Drop that file here — iPhone and Android exports are both accepted.
PDFs freeze a chat into pages; Markdown keeps it as structured text you can search, quote, version-control and import into note apps like Obsidian or Logseq. Print or export to PDF later from any Markdown app if you need pages.
The .zip's media filenames are listed in an Attached media files manifest so nothing goes missing; match them against your unzipped export folder. Text and timestamps are fully converted.
Probably not this tool's fault: iPhone Export Chat silently truncates around ~40,000 messages, and With Media exports can fail on size first. For very long chats, export Without Media.
No. Parsing and rendering happen entirely inside your browser — unlike most chat-to-PDF sites, your messages never touch a server.
TXT Document (TXT) and Markdown Document (MD) serve distinct roles across the digital workflow. Converting to MD provides optimized compatibility, modern compression efficiency, or standardized playback across web browsers, operating systems, and media production environments.
The output format (MD) is inherently lossless or supports lossless operation. Your original visual or audio fidelity is mathematically preserved without quantization artifacts.
Never. convrtr is architected with a strict zero-upload model. All processing, decoding, decompression, and encoding happen 100% locally on your machine using sandboxed WebAssembly and Web Workers. Your data never touches an external server, database, or analytics collector.
You can execute this conversion locally via command-line utilities such as ffmpeg, cwebp, or ImageMagick. For example: see the developer terminal recipe provided in the technical specifications dossier above. convrtr provides the identical local-first capability directly inside your browser without installing CLI packages.
Yes. You can drop multiple .txt files into the instrument to process them concurrently in browser Web Workers, or click 'Open in Master Studio' to queue mixed formats, configure individual targets, and export as a single ZIP archive.
Convert web media, local files, and document assets directly in Chrome Side Panel using client-side WebAssembly, zero-server uploads, and the official convrtr browser extension.
A byte-level walkthrough of the MLW container format: the Root marker, the filename block, the AES-GCM payload, and the one part of the layout nobody has documented.
MLW uses a single fixed encryption key shared across every install of the app. What that means for whether unwrapping it counts as DRM circumvention — in plain English, not legal advice.