Skip to main content
Files is your organization’s shared media library. A file can enter the library because you uploaded it or because a phone session captured it. Every ready file has one ID and can be downloaded locally or delivered to a phone.

The file model

Upload and capture describe provenance. They are not separate libraries. Uploaded and captured files share the same ID space and delivery flow.

Limits and lifecycle

  • The library accepts supported image and video formats.
  • A library file can be up to 100 MiB, which is also the phone-delivery ceiling. Files stored under the earlier 1 GiB library limit remain listed, but a push still refuses anything over 100 MiB.
  • Every library listing reports the organization’s current file-count and byte usage against its quota. Treat those returned limits as authoritative.
  • An upload becomes usable after its bytes are verified and its status reaches ready.
  • A capture has a more detailed capture_state. It can remain visible even when the phone skips it or the transfer fails.
  • Download URLs are short-lived. List the file again to obtain a new URL after one expires.
Search and filter the library instead of navigating folders. You can filter by source, capture surface, session, MIME type, size, and creation time. You can sort by creation time, filename, size, or source.

Open the library

Open Files for your organization. The organization-specific route is /dashboard/<organization-slug>/files.The page shows uploads and captures together. Filter by source, search by filename, switch between grid and list views, and inspect live quota usage.
Use the axilio files command group in new scripts. Older directional CLI groups remain hidden compatibility aliases, not the current interface.

Next steps

Move files

Upload, download, push, rename, and delete files.

Session captures

Find files that a session captured from its phone.