Large file distribution (>2 GB) to managed devices: Content Management limit and workarounds

Android

Title: File upload fails above 2 GB — Content Management limits and workarounds

When uploading a file larger than 2 GB to Esper Content Management, the upload is rejected and the file is not distributed to your devices.

Why this happens

Esper enforces a hard upload limit of 2 GB per file in Content Management and 50 MB per file in File Manager. Files such as full firmware packages often exceed these limits and must be reduced in size or distributed through an alternative method before they can reach your managed devices.

Option 1: Compress the file below 2 GB

If your file is only slightly above 2 GB, lossless compression may bring it within the limit without any data loss.

1. Compress your firmware or update package using a tool such as 7-Zip at its maximum compression setting. Lossless compression preserves the file's integrity while reducing its size.
2. Confirm the compressed file is under 2 GB before proceeding.
3. Navigate to Content Management → Add Content in the Esper Console and upload the compressed file.
4. Open the Blueprint you want to use: go to Blueprints → [Blueprint Name] → Content → Add File and select the uploaded file.
5. Apply the blueprint to your target devices: go to Devices & Groups → [Group Name] → Blueprint → Apply.

Verify: On the target device, confirm the file is present at your configured destination path. For Android devices with ADB access, run:

adb shell ls -lh /sdcard/

The file should appear at the expected path within a few minutes of the blueprint being applied.

Option 2: Use a vendor-provided split or delta update

If compression is not possible or does not reduce the file enough, check whether your firmware vendor provides a smaller alternative package.

1. Check your firmware vendor's support portal for a split-package, delta, or incremental OTA update. These packages contain only the changes between firmware versions and are typically far smaller than a full image.
2. If the resulting files are each under 2 GB, upload them individually via Content Management → Add Content and distribute them using a Blueprint as described in Option 1.
3. For Zebra devices specifically, evaluate whether Zebra LifeGuard OTA can manage firmware updates independently while Esper continues to enforce all other device policies.

Verify: After applying the update package, confirm the device reports the expected firmware version in Devices & Groups → [Device Name] → Device Info.

Option 3: Request a higher upload limit

If neither option above resolves your situation, Esper can evaluate a Content Management limit increase for your account on a case-by-case basis.

1. Gather the following information before contacting support:
   • The exact file size and file type (for example, Zebra TC53E full firmware image, 2.80 GB)
   • Why the file cannot be compressed or split
   • The number of devices and groups that need to receive the file
2. Submit a request to Esper Support with the details above. Providing this information upfront avoids back-and-forth and speeds up the evaluation.

Verify: Esper Support will confirm in writing whether a limit increase has been applied to your account. Once confirmed, retry the upload via Content Management → Add Content.

If this doesn't resolve it

If the upload still fails after trying the options above, contact Esper Support and include:

• The file size and file type
• The exact error message or behavior observed during upload
• Which options you have already attempted and the outcome of each

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.