Client delivery
Send the approved exports in the formats and sizes agreed for the commission.
File sharing for photographers
A complete shoot.
A personal delivery.
Deliver original images and complete shoot packages to clients and agencies.
Named recipients · Defined access · Recorded activity
MX / CONTROLLED EXCHANGE03
Assemble the approved package.
↗
Client-Shoot-Final-Images.zipIllustrative file package
MXTHE EXCHANGE IN CONTEXT
Give the handoff some context.
Original images and final exports can be commercially sensitive before publication. Deliver the agreed selection to named client contacts with clear usage and package notes.
MX provides a route for sensitive business files between named recipients. Match access conditions to the purpose of the exchange and use the available activity record to support follow-up. Keep the underlying approval and information-handling decisions in your own process.
WHERE THE WORKFLOW HELPS
The moments that need a handoff.
Agency handoffs
Share selected originals or production files with the appointed creative team.
Retouching exchanges
Provide the source material and instructions needed by an external retoucher.
A HANDOFF, IN PRACTICE
The right files.
The full context.
A photographer is delivering a commissioned collection to a client. Separate final selections from outtakes and working edits. Organise the exports by intended use and state whether each set is prepared for print, web or another agreed purpose, so the client can choose the right version.
Illustrative workflow · Adapt to your approved process
Deliver a finished photography collection
↗Client-Shoot-Final-Images.zip
A POSSIBLE PACKAGE
- ✓Selected final images
- ✓Image inventory
- ✓Usage and format notes
INTENDED RECIPIENT
The client's appointed image or production contact
A USEFUL RESULT
The client can match the selections to the inventory and distinguish the export sizes and intended uses.
MAKE THE FIRST EXCHANGE COUNT
Test the details.
Then repeat with confidence.
Use the example package as a starting point for a small, representative trial. Agree the success criteria with the person who will actually receive the files.
Check completeness
Selected final images should be easy to identify in the inventory. Open the delivery copy independently of your working folder to catch missing files or local dependencies.
Walk through access
Test with the intended recipient role and receiving environment. Confirm the access conditions, the instructions and the route for getting help.
Agree what success means
The client can match the selections to the inventory and distinguish the export sizes and intended uses. Record any remaining questions before making the exchange part of routine work.
FROM PREPARATION TO RECEIPT
Give each exchange
a clear sequence.
Use Client-Shoot-Final-Images.zip as an example of a defined package. Replace it with the approved files and instructions for your actual task.
Explore the MX feature set ↗- 01
Confirm the purpose and recipient
Check who is entitled to receive the information. Record the business purpose through your normal approval process before assembling the package.
- 02
Prepare an approved package
Choose the required files, check their versions and remove unrelated information. Include concise instructions so the recipient knows what to do next.
- 03
Apply the access conditions
Confirm authentication, availability and any download conditions for your service. MX's existing features include named access, MFA and configurable expiry controls.
- 04
Review the exchange
Check the recorded activity and follow up through the agreed process. Keep the exchange reference with the project or client record it supports.
DEFINE THE BOUNDARY
Check the fit
before the first file.
Confirm licensing, model releases and embargoes before delivery. Keep originals and backups in your established archive rather than treating a transfer as your only copy.
Assess the controls against a representative package and recipient. Confirm any mandatory capability, contract term or deployment requirement with the MX team before relying on it.
Discuss your exchange requirements ↗PRACTICAL QUESTIONS
What to know
before you begin.
Questions about file sharing for photographers and the exchange workflow.
Should RAW files be part of the package?+
Follow the agreed commission and usage terms. RAW files, working edits and third-party assets need a deliberate release decision; they should not enter the delivery simply because they share a folder with final exports.
Does MX provide an online client gallery?+
Assess MX for controlled file exchange. Gallery presentation, image selection, proofing and print fulfilment are separate requirements to check.
How should we prepare the files?+
Send the approved exports in the formats and sizes agreed for the commission. Check the approved version, any required dependencies and the recipient's ability to use the package. Include only the material needed for the purpose.
What should we verify during a trial?+
Test a representative exchange from sender preparation to recipient access. Check authentication, permissions, expiry behaviour and the activity available afterwards. Include the actual file types and recipient environment you expect to use.
Does an access expiry remove downloaded copies?+
Do not assume expiry deletes a recipient's local copy. Agree post-download handling and retention responsibilities, and confirm the precise behaviour of the service configuration you plan to use.
Where can we check product details and commercial terms?+
Use the current MX product information and confirm the proposed service with the team. Review the plans and pricing alongside your actual users, workflow and deployment requirements.
YOUR NEXT EXCHANGE STARTS HERE
Valuable data.
Better protected.
Put better controls around your next sensitive file exchange. See how MX fits your organisation's workflow.
7 days freeUp to 5 usersNo credit card
- Full feature access
- Unlimited file size transfers
- Named recipients and MFA
- Custom branding and upload portals