Download this page as .mdz

Help test MDZip

MDZip's apps are tested by their developers, but that's a handful of computers. You can help by following a short test script on yours and saying what happened. No coding, and no need to know anything about MDZip beforehand.

How it works

  1. Pick a script from the list below, for an app and a computer you have.
  2. Follow the steps. Each one says what to do and what you should see. When something looks different, note the step number and what you saw. A screenshot helps.
  3. Post your results in Test reports. A short form asks which script you followed, the app version, your computer, and what didn't work. You need a free GitHub account.

A report where everything passed is useful too: it tells us the app works on a computer we haven't tried. If a step fails, we'll turn it into a bug report for that app and reply in your post.

Test scripts

Script What it checks Time
MDZip Studio on Mac Installing Studio on a Mac, opening .mdz files from Finder, editing, pictures, the Mac menus and the Dock About 20 minutes
MarkItDown converter Turning .mdz files into plain Markdown with Microsoft's MarkItDown, and Word, PowerPoint and web pages into .mdz files with their pictures. Windows, Mac or Linux About 30 minutes
Pandoc converter Turning .mdz files into Word, web pages and e-books with Pandoc, and Markdown and Word files into .mdz files with their pictures. Windows, Mac or Linux About 30 minutes

Intel Macs are especially welcome: Studio hasn't been tried on one yet.

The converter scripts are on GitHub, next to each converter's code. You'll type commands into a terminal, but you don't need to write code.

Want a script for another app or computer? Ask in Discussions.

This page renders from testing.mdz (MDZip, ~3 KB, updated 2026-11-10) — one self-contained file. Download it, open it in the web editor, or read how these pages are made.