Deliver a client file pack that makes sense without you
Package approved exports, editable sources and useful notes into a portable ZIP with one free archive tool.
One versioned ZIP containing approved files, a clear inventory and a short delivery note, checked after extraction.
The handover is part of the design. Before buying another delivery portal, make a small package that tells the recipient what to open, what to reuse and what has separate conditions. This original FreeStack exercise uses a fictional Bramble identity pack, not real client work or a tested archive. Provider sources checked 18 October 2026.
Free boundaries before you start
Source checks for this workflow. These notes clarify older catalogue summaries; they do not change your saved toolkit.
PeaZip · checked 2026-10-18
Ongoing free LGPLv3 desktop archive manager for private and professional use on Windows, macOS and Linux. Creates ZIP and other supported archives; bundled engines and optional plugins keep separate notices. RAR extraction is included, but RAR creation requires installed WinRAR. Local archive work is separate from any hosting or delivery service.
The documented local archive workflow has no hosted-account step; official download links are public. This does not establish account requirements for any separate delivery service.
A small example to aim for
bramble-handover-v1.zip
bramble-logo-dark.svg
bramble-preview.pdf
bramble-identity-v1.svg
Compatible editor required
README.txt
Asset sources + licence notes
Open. Understand.
Reuse the right file.
One named version. Approved exports.
A short note that travels with the work.
FreeStack layout concept, not a provider screenshot or a completed client handover.
FreeStack example output · illustrative, not a provider screenshot or a tested export.
Jump to a step
Agree what the recipient actually needs
Write a short delivery checklist before gathering files. For our fictional identity project, the client needs approved viewing files, the editable artwork agreed in scope and notes about the fonts and images. Ask which formats and delivery channel they can use. Do not promise that a source file becomes editable without compatible software, or that every licensed asset can be transferred. Keep unrelated drafts, personal data and credentials outside the handover folder.
Separate ready-to-use files from working sources
Make one clearly named project folder with a version, such as bramble-handover-v1. Inside it, separate Ready-to-use, Editable-source and Notes. Choose filenames that explain purpose, colour variant and version rather than final-final. Copy only the approved exports and agreed sources into this folder, leaving your working originals safely elsewhere. Open the copied exports to check they are the intended files. For linked images or fonts, document what the recipient must obtain rather than bundling assets without permission.
Write a readme that answers the first questions
Use a plain-text editor already on your device to create README.txt in Notes. Explain which files are for immediate use, which need an editor, what the filenames mean and how to request a revision. Include a short inventory and any relevant asset-source links or licence notices. If an asset is deliberately excluded, say why and how it can be obtained. Write the note for the recipient, not for someone who has followed every design meeting. Never put passwords or private access tokens in the readme.
Create a simple, compatible archive
Download PeaZip through its official project links for your operating system. Select the staged folder and choose Add. Set the archive type to ZIP, keep the standard Deflate compression method and create a single archive in a separate output location. Give it the same project version. Avoid unusual compression methods or a self-extracting executable for this ordinary handover. Already-compressed PDFs and images may shrink very little; packaging is still useful even when compression saves little space. Keep the original files after archiving.
Check the archive, then check the extracted files
Open the ZIP in PeaZip and inspect the folder names and inventory. Run its archive integrity test to look for corruption, then extract into a new empty folder. Compare that extracted folder with the readme and open the actual viewing files, not the copies still in your working folder. Where possible, ask the recipient to check extraction and one representative file on their own system. An archive test does not prove that you included the right design, cleared asset rights or removed confidential data; those need separate review.
Send the package and name any remaining gap
Use the client’s existing approved transfer channel, within its size and access limits. State the ZIP filename, version, contents and any required next action. Keep a separate backup of the source and delivered package. FreeStack editorial upgrade triggers: consider paid managed delivery only for a specific recurring requirement such as controlled access, expiry, a review audit trail or files that exceed your agreed transfer channel. A ZIP is packaging, not a private portal, backup service or permission system.
Your workflow, connected.
Follow the steps and carry the output into the next stage. These are suggested handoffs, not automatic integrations.
- 04Package once
PeaZip packages and inspects local files; it does not provide hosted delivery or client accounts.
Versioned ZIP
Provider information
Check current plans and documentation before committing to a workflow.
View 6 provider links
- PeaZip: LGPLv3, professional use and official download links
- Official archive-creation workflow
- Official ZIP support, Deflate compatibility and integrity testing
- Official archive browsing, content lists and test controls
- Official extraction workflow
- Separate encryption guidance and compatibility limitations
A couple of useful questions
Is PeaZip free for commercial client work?
The official project states the LGPLv3 application is free for private and professional use. The local archive workflow has no provider storage or monthly export allowance. Your hardware, disk space and separately obtained assets remain separate.
Will the recipient need PeaZip?
Ordinary ZIP with standard Deflate is intended for broad compatibility with ZIP utilities, but you should still check the recipient’s actual system. Unusual compression methods or encryption can need additional support. This guide does not use a self-extracting program.
Does a successful integrity test mean the handover is finished?
No. It checks archive data, not editorial completeness, malware safety, licence clearance or whether the recipient can edit the source. Inspect the inventory and extracted files separately.
What does Save this toolkit save?
The existing FreeStack flow saves the PeaZip listing to your private stack after sign-in. It does not upload, store or share the client’s files. Keep your ZIP and backup in your own approved storage.
What would you try?
Share your result or ask a specific question about this workflow.
Join the conversationKeep building
Make a portable creative CV before buying another subscription
Build a focused one-page CV with an editable source, checked typography and a PDF you can inspect before sending.
ExcalidrawMap a client approval workflow before buying automation
Turn a messy feedback loop into one readable diagram and a clear decision about what needs automating.