Mac file transfer

How it works

ZIP from the Finder adds __MACOSX. AirDrop works to other Apple devices. SFTP and browsers work everywhere. Resource forks rarely matter and often confuse. Pack without them unless a Mac app needs them.

A Finder zip of 200 assets uploads cleanly and unzips on Windows with a junk folder. A zip from the command line without AppleDouble does not. They change the packager, not the protocol.

How it differs

Mac file transfer is not AirDrop. AirDrop is one nearby option.

APFS features do not survive a bucket. Send bytes you can name.

Test the unzip on the destination OS.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For mac file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive mac file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.