Skip to main content
Moving a file is a two-part operation:
  1. Upload stores the local bytes once in your organization’s library.
  2. Push creates a delivery from that library file to a phone.
You can push the same file to several phones without uploading it again. You can also use a one-shot send helper when you do not need to retain the two steps separately.
Both the library and phone delivery cap a file at 100 MiB. An upload larger than that is rejected before any bytes transfer, and a one-shot Python or Go send refuses an oversized file without uploading it. Files stored under the earlier 1 GiB library limit stay in the library, but a push to a phone still refuses anything over 100 MiB.

Upload and push

Open Files for your organization and choose Upload Files, drag files onto the page, or upload from the Files tool during a workflow or session.During an active session, open the Files tool, select a library file, and choose Send. The delivery reports progress and reaches delivered or failed after the phone responds.
Delivery status moves from dispatching to dispatched, then to delivered or failed. The phone may also report bytes_transferred while a delivery is in progress.

Download a file

Only a ready file has a download_url. The URL is short-lived and needs no Axilio authentication header.
On Files, choose the download action on a ready file. Selecting a preview opens the original in a new tab.

Rename an uploaded file

Only source=upload files can be renamed. A capture keeps the filename that the phone reported because it is part of the capture’s provenance. Renaming is metadata-only: existing URLs still work, and earlier deliveries retain the name they used at push time.
On Files, use the rename action beside an uploaded filename. Captured filenames have no rename action.
The CLI does not have a post-upload rename command. Set the stored name during upload with axilio files upload <path> --filename <name> or use one of the rename interfaces above.

Delete

Deleting a file removes it from the library and frees its quota. Copies already on phones are not touched, whether the file was pushed to a phone or captured from one. Removing a file from a phone is a separate operation and is not available yet.
Open Files and choose the delete action on the file. The confirmation shows how many phones were sent a copy; those copies stay on the phones.
Deleting a captured file removes the library copy only. The media stays on the phone it was captured from, and on any phone it was later pushed to.