Share PSD, Blender and ZIP rewards without exposing private files

Decide what the reward actually includes

Scroll the table sideways to see all columns.

Build the package in a separate release folder

1. Write a short contents list for the promised reward. Decide whether members get an editable source or only a finished export; those are different deliverables.
2. Create a new release folder and copy in only the intended files. Do not compress the whole working directory and then rely on its folder name to describe what is inside.
3. Review the release copy’s layers, notes and metadata. Keep creator credits you want to publish, but remove unintended personal details from that copy. Preserve the working master separately.
4. Give the release a clear name and version. Add a short readme describing the included files, required software and known dependencies without exposing your local account details.

Check what the editing application saves

Photoshop’s Save a Copy can preserve your original while creating a separate deliverable. A layered source can retain more information than a finished image. Export options also affect metadata, so inspect the actual chosen output rather than assuming every format contains the same information.

Blender projects may depend on external resources or contain packed data. Review the documentation for your installed version and list the dependencies needed by the recipient. Packing is not a privacy audit, and not every resource is necessarily included. Check which third-party assets you can share before adding them.

Test the archive as a recipient

1. Create the final archive from the release folder. Extract it into another empty test folder, then inspect that extracted copy instead of the working project.
2. Open the intended files and check for missing assets, unwanted content and links to private working locations. Keep your original folders untouched; use a separate test environment where practical.
3. After uploading, download the published file yourself and repeat the check. Verify the archive contents, version and destination folder, not just that the upload completed.

A ZIP archive is a package, not a membership check. A renamed or compressed file can still contain the same private material.

Control access to the checked release

Put the checked package at the intended storage destination. Create a clearly named TierKey link and select the allowed Patreon tiers. Share that entry link in the relevant post, then ask an eligible member to test the actual download route.

TierKey does not inspect archives, remove metadata, sanitize project files or store the reward. Its history records redirects through the entry link, not which file inside an archive was used. If the package was wrong, replace it at the storage service and tell members which version to use; saved copies cannot be recalled by changing the link.

These screenshots use the English interface. Match each number to its explanation. Select an image to enlarge it. Names, URLs and member records are examples.

English interface exampleEnlarge image

English interface example · New protected linkClose

Scroll up, down or sideways if the image does not fit.