Hero screenshot
Use a clean app state with the package loaded and groups visible.
Case study
Drawing package cleanup.
Use this page as the case-study pattern for measured before-and-after workflows. Replace placeholder notes with real screenshots, file counts, export names, and timing once captured.
Publishing rule
Do not claim time saved, file-size reduction, or error reduction until the result is measured from a repeatable sample run.
Scenario
A user receives a package containing mixed drawings, site images, PDF pages, and supporting files. The goal is to produce a clean combined PDF for review, split PDFs by group, and a sorted ZIP for filing.
Workflow
- Open the package locally. Drop the archive or select it from disk. unzipzapp lists supported files in the browser.
- Review detected groups. Confirm automatic grouping, rename groups if needed, and adjust prefix rules for project naming.
- Clean the order. Use Custom order to reorder files and exclude unrelated items before export.
- Choose outputs. Build a combined PDF, split PDFs, and a sorted ZIP when the job needs both review and filing packages.
- Save and archive. Download exports or save to a workspace folder in Chrome or Edge.
Before and After Evidence
| Evidence | What to capture |
|---|---|
| Input package | File count, file types, total size, and a screenshot of the loaded group preview. |
| Cleanup decisions | Group names, excluded files, custom order changes, and selected output recipe. |
| Output package | Export filenames, output sizes, page counts, ZIP layout, and post-export status. |
Reusable Assets
Workflow video
Keep the recording focused on the actual cleanup, not a product tour.
Proof table
Use measured file counts, export names, and sizes. Avoid vague savings claims.