15 September 2026
Converting ClarisWorks and AppleWorks CWK to Markdown: Recovering Vintage Mac Documents
Throughout the 1990s and early 2000s, ClarisWorks (later rebranded by Apple as AppleWorks) was the premier integrated office suite bundled with Macintosh computers, iMacs, and PowerBooks. It seamlessly integrated word processing, spreadsheets, databases, presentations, and vector drawing into single compound documents ending in .cwk.
Millions of family histories, legal records, university dissertations, and creative writing projects were authored in ClarisWorks. However, when Apple transitioned from Motorola 68k and PowerPC architectures to Intel and eventually Apple Silicon, AppleWorks was discontinued and left unsupported.
Modern macOS and Windows systems cannot natively open .cwk files.
This technical guide analyzes the ClarisWorks / AppleWorks binary container, explains how MacBinary II encapsulation and Mac OS Roman typography work, and demonstrates how convrtr's CWK to Markdown converter resurrects your text into modern, portable Markdown files directly in your web browser.
The MacBinary II Encapsulation
When vintage Mac files were archived, emailed, or transferred to non-HFS filesystems, they were often wrapped in a MacBinary II 128-byte container. The MacBinary header preserves vital Macintosh filesystem metadata:
- Offset
0x00: Format version check (0x00). - Offset
0x01–0x40: Original Macintosh filename (Pascal string). - Offset
0x41–0x44: File Type code (e.g.,"CWWP"for ClarisWorks Word Processing). - Offset
0x45–0x48: Creator code (e.g.,"BOBO"for ClarisWorks). - Offset
0x53–0x56: Length of the Data Fork in bytes. - Offset
0x7A–0x7B: Format secondary check signature ("mB").
convrtr automatically detects and strips MacBinary II headers, locating the start of the ClarisWorks document payload without requiring third-party unarchivers.
ClarisWorks Document Identification
Inside the data fork, ClarisWorks and AppleWorks documents begin with signature magic sequences identifying the component type:
| File Signature | Document Environment | Application |
| :--- | :--- | :--- |
| 0x00 0x01 0x00 0x00 | Word Processing (CWWP) | ClarisWorks 1.0–5.0 |
| 0x00 0x02 0x00 0x00 | Drawing (CWGR) | ClarisWorks |
| "BOBO" | Proprietary Resource Map | ClarisWorks Suite |
| "AppleWorks" | AppleWorks XML/Binary | AppleWorks 6 |
Typography and Mac OS Roman Decoding
Unlike modern UTF-8 documents, vintage ClarisWorks documents were encoded in Mac OS Roman. Special typography like curly quotes (“ ”), em dashes (—), and accented vowels (é, ü) use vintage character mappings:
0xD2/0xD3: Left and right double quotation marks (“and”).0xD4/0xD5: Left and right single quotation marks (‘and’).0xD1: Em dash (—).0xA5: Bullet point (•).
convrtr's engine maps all Mac OS Roman codepoints accurately to standard Unicode, ensuring that quotes and foreign language accents appear crisp and readable.
Conversion to GitHub Flavored Markdown
The extraction engine analyzes paragraph breaks, line lengths, and list indicators. Bullet symbols (•) are formatted into clean Markdown lists (- item), title lines are converted into semantic headers (# Title, ## Subheading), and consecutive whitespace is neatly normalized.
The resulting Markdown file can be opened in Obsidian, Notion, GitHub, or any modern markdown editor with zero loss of content and complete privacy.
Related reading
Converting Emacs Org Mode to Markdown: Outlines, Tables, and Checklists
Explore the syntax and semantics of Emacs Org Mode (.org). Learn how asterisk headings, TODO states, priority tags, Org Calc tables, and code blocks translate to GitHub Flavored Markdown.
Converting Evernote ENEX Notebooks to Markdown: Free Your Notes from Proprietary XML
Learn how Evernote XML Export (.enex) files structure notes, timestamps, tags, and ENML layout markup, and how to convert them into clean GitHub Flavored Markdown with YAML frontmatter.
Converting OPML Outlines and Subscriptions to Markdown: Tables and Hierarchies
Dissect the Outline Processor Markup Language (.opml) architecture. Learn how RSS subscription directories, podcast feeds, and hierarchical task outlines are converted into clean GitHub Flavored Markdown.
Converting FictionBook 2.0 (FB2) E-Books to Markdown: XML Structure and Semantics
Explore the FictionBook 2.0 (.fb2) architecture. Learn how semantic XML e-book structures, epigraphs, poems, footnotes, and metadata are converted into clean GitHub Flavored Markdown.
Converting AbiWord (.abw, .zabw) to Markdown: Open-Source Word Processing Recovery
Examine AbiWord's native AWML XML document architecture. Learn how Dublin Core metadata, 2D table grids, styled character spans, GZIP compression, and base64 illustrations convert into clean Markdown.
Converting Hangul Word Processor (HWP) to Markdown: OLE CFB & Deflate Forensics
Unpack Hancom Hangul HWP 5.x compound documents. Discover how OLE 2.0 CFB directory tables, Deflate stream decompression, and HWPTAG_PARA_TEXT record parsers extract clean Markdown in browser memory.
Converting OpenOffice SXW to Markdown: Unpacking Pre-ODF XML Document Archives
Learn how OpenOffice.org 1.x and StarOffice Writer (.sxw) XML packages work. Discover how to extract text, tables, and lists into clean Markdown directly in your browser.
Converting StarOffice & StarWriter (SDW) to Markdown: OLE Compound Binary Forensics
Recover text, headings, bullet lists, and metadata from vintage StarOffice 3.x–5.x (.sdw) word processing documents. Learn how OLE CFB streams unpack to GitHub Flavored Markdown.
Converting Compressed AbiWord (ZABW) to Markdown: Gzip XML Document Extraction
Learn how AbiWord's compressed .zabw document format packages rich word processing XML inside Gzip containers, and how to convert it to clean GitHub Flavored Markdown.
Converting Apple RTFD Bundles to Markdown: Rich Text & Attachment Extraction
Learn how Apple macOS RTFD compound packages bundle Rich Text Format documents with graphic attachments, and how to convert them into GitHub Flavored Markdown 100% offline.