Project files · Ready for the next step
Big files.
A simpler handoff.
Share media, design assets, and project files with XMLA. Add your client details and a short note so we know which project the files belong to and what needs to happen next.
27 years in business. Keeping your files and project connected.
Before You Upload
Give the files enough context to land in the right place.
Large uploads move faster when XMLA can connect them to the right client, website, ticket, launch, or production task.
Name the project
Use the same business, website, ticket, or project name XMLA already has on file.
Add contact context
Enter the client name and email XMLA should use when matching files to the request.
Summarize the files
Use project notes to explain what the upload contains and where the files belong.
Use for large assets
Send media packages, archives, source files, video, design files, and other larger uploads here.
Best Fit
Use this portal for files that are too large or too important for email.
The upload path is built for production assets, source files, and larger packages that need to stay attached to the right XMLA workflow.
Media Packages
Photos, videos, audio, galleries, compressed folders, and source media for production work.
Design Assets
Logos, PSD, AI, EPS, print files, screenshots, mockups, and brand documents.
Website Content
PDFs, documents, spreadsheets, slides, downloads, and content packages for site updates.
Project Archives
ZIP packages, export files, backups, reference bundles, and implementation materials.
Secure Upload Portal
Send large files to XMLA.
Enter your client details, add notes, continue to the upload area, then drag files into the portal or click to choose them from your device.
For copy changes, page instructions, and smaller file attachments, use the Submit Content page so the production request and files stay together.
Transfer Flow
Large files need a clear production trail.
The upload portal keeps the asset transfer separate from the website server while still giving XMLA the context needed to process the files.
Identify
Add your client details and notes so XMLA can connect the upload to the right request.
Upload
Drop files into the secure portal or click to select files from your device.
Transfer
Files are sent through the secure Dropbox-backed API and are not stored on the website server.
Review
XMLA checks the received files and follows up if anything is missing or unclear.
Related Paths
Choose the right intake for the rest of the request.
Large files are only one part of the workflow. Use these routes when XMLA also needs instructions, support context, onboarding, or ongoing care.
Submit Content
Use this when the request includes page instructions, copy, and smaller attachments.
HelpSupport Center
Use support if the upload relates to an urgent request, active ticket, or service question.
StartQuick Start
Use onboarding when uploads are part of a new customer setup or migration.
CareXMLA Care
Use managed care for recurring updates, content publishing, and production support.
Managed Production
Files are useful when the instructions are clear.
If this upload belongs to a website update, launch, repair, migration, or managed service task, include the related ticket, page URL, or project name in the notes.