Protect the distribution copy, not the master
Keep your master version unchanged and create a separate client-sharing copy.
That copy is where passwords, reduced size, and share-specific naming belong.
Use layered controls
Passwords help, but they are only one layer. Expiry windows, limited recipients, and clear versioning reduce the real-world risk of uncontrolled spread.
If the file is too large, compress before sharing so the recipient does not end up forwarding multiple versions.
Frequently asked questions
Does password protection replace secure delivery?
No. It is one control, not a full delivery model. The surrounding workflow still matters.
Should I protect the original archived file?
Usually no. Keep the archive copy clean and apply protection to the outward-facing distribution copy.