Skip to main content

0.2.18: Recursive folder downloads

Use cesiumcloud download FOLDER --location DESTINATION to restore a cloud directory beneath DESTINATION, preserving all nested subfolders, files and explicitly empty folders. The folder keeps its name; when a matching local directory already exists, a numbered new folder is chosen to avoid overwriting existing data. This works on Windows and Linux, and preserves existing single-file downloads, parallel workers, and the full-account --all command.

CesiumCloud v0.2.0

CesiumCloud lets you upload, download, rename, and delete cloud files and folders.

Service: https://cloud.cesiummc.space/app/ API: https://api.cesiummc.space

CLI

Authenticate with cesiumcloud authenticate. Your credentials are local and can be revoked.

  • cesiumcloud upload "path/to/file-or-folder"
  • cesiumcloud list -a
  • cesiumcloud search notes.txt
  • cesiumcloud dir images
  • cesiumcloud download "restore-directory"
  • cesiumcloud download images/photo.png --location "restore-directory"
  • cesiumcloud rename old.txt new.txt
  • cesiumcloud move old.txt to root/archive
  • cesiumcloud delete root/archive/old.txt

Uploads transfer in resumable 64 MiB chunks using a short-lived authorization grant. Individual files can be downloaded, replaced and permanently removed from active storage without rebuilding other files.

JavaScript SDK

const { IsolatedTransferClient } = require("cesiumcloud");
const storage = new IsolatedTransferClient(process.env.CESIUMCLOUD_API_KEY);
await storage.uploadFile("notes.txt", "docs/notes.txt");
const files = await storage.allFiles();
await storage.download(files[0].id, "./restored.txt");
await storage.delete(files[0].id);

Python SDK

import os
from cesiumcloud import IsolatedTransferClient
storage = IsolatedTransferClient(os.environ["CESIUMCLOUD_API_KEY"])
storage.upload_file("notes.txt", "docs/notes.txt")
files = storage.all_files()
storage.download_file(files[0]["id"], "restored.txt")
storage.delete_file(files[0]["id"])

Existing CesiumCloudClient high-level upload and download methods also use isolated file storage.

Optional local encryption

Use cesiumcloud e2ee keygen to generate a local recovery key, and cesiumcloud e2ee upload FILE to encrypt locally before upload. The server cannot recover your key. Keep an offline backup. Encryption protects contents, not filenames or sizes. The .ccenc format is authenticated and cross-platform.

Notes

Deleting a cloud file is permanent. Stopping an upload permanently removes its unfinished data and releases its reservation. Keep offline backups of important files.

Replacement and upload cancellation (0.2.1)

Use cesiumcloud upload --replace "file.txt" (or a folder) to replace a matching virtual path, or create it normally when absent. The SDK accepts replace=True in upload_file and upload_path and has cancel_upload(upload_id). Use cesiumcloud cancel-upload UPLOAD_ID or Ctrl+C on an active CLI upload. Already completed files are preserved. The website's ReplacedFiles history is separate from the CLI flag.

Version 0.2.10

The dir command validates its destination against the authenticated server catalog, including explicitly created empty folders. Deleted and trashed directories are rejected even when another terminal or browser tab still has an old folder view. The server rejects new uploads to invalid directories at both upload admission and file commit.

0.2.11: parallel uploads

Directory navigation remains authenticated against the server, including empty folders, with trashed or deleted destinations rejected. Uploading folders and multi-source selections now defaults to up to 40 simultaneous uploads while preserving account upload limits and ordinary file operations. The first set of 40 uploads is registered and transfers start immediately; subsequent registrations overlap with active transfers rather than blocking on admission for every selected file. Explicit -simultaneous N retains concurrency control, capped at 40 for uploads. Single-file uploads retain their live progress behavior. Incremental aggregate byte counters and throttled terminal refreshes avoid rescanning thousands of entries per update. Unused reservations are cancelled on interruption or partial failure.

Metadata

Release files for cesiumcloud 0.2.18

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cesiumcloud 0.2.18
File Size Uploaded Provenance Actions
cesiumcloud-0.2.18.tar.gz 70.2 kB With provenance Details for cesiumcloud-0.2.18.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cesiumcloud 0.2.18
File Interpreter ABI Platform Actions
cesiumcloud-0.2.18-py3-none-any.whl Python 3 none any Details for cesiumcloud-0.2.18-py3-none-any.whl

Total release size: 123.3 kB

Release files / cesiumcloud-0.2.18.tar.gz

Download URL cesiumcloud-0.2.18.tar.gz
Size 70.2 kB
Tags Source
SHA-256 checksum
How to use checksums
64410ef99831d76b846ae77cfed2c12ba781cb79a68466caa646d659e771d26e
BLAKE2b-256 checksum
How to use checksums
92203beca3f07bfd64931e8dac6aba797ad21aa2734695f6f490fa0097e7e67d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / cesiumcloud-0.2.18-py3-none-any.whl

Download URL cesiumcloud-0.2.18-py3-none-any.whl
Size 53.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
97e5e2b28c064afb2d35b2ca1343edef4f8854f940455e410aed5ee411c93da6
BLAKE2b-256 checksum
How to use checksums
522e0ab9b4701a804709c5e617dc494fc1cdcc96ba7ab002fba59e1be4054621
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for cesiumcloud 0.2.18

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cesiumcloud-0.2.18.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.18 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page