Bring your downloads into order.

Bring the collection into a clear queue

Flux is a workspace for collecting authorised files and following each transfer to a useful result. Start with a direct link, a batch or a prepared download manifest, then keep queued, active, paused, failed and completed items distinct. A clear queue makes missing inputs easier to find before they disrupt another task.

Use Flux when a project depends on several source files or when a large transfer needs visible progress and recovery. Keep the source and usage rights alongside the task. Download management does not grant access to material that the origin restricts or that you are not permitted to copy.

Choose supported links and meaningful names

Direct downloads accept public HTTP and HTTPS file URLs. Supported cloud transfers include HTTP, HTTPS and plain FTP; FTP is unencrypted, so prefer an authorised HTTPS source when available. Unsupported FTPS, SFTP, SSH, torrent and premium-unlocking tasks are rejected rather than represented as successful transfers.

A page address is not always a downloadable file address. Check the origin, any access requirements and the expected output before queuing many links. Avoid posting private credentials or signed source URLs into public messages. Give each batch a useful purpose so it remains understandable when you revisit it.

Follow individual transfers, not just the total

• Submit a link or batch once and inspect its accepted count and individual errors. A later list-refresh error does not mean the first submission never committed.
• Filter the queue and pause, resume or retry the item that needs attention. Segment details appear only when actual segment records exist.
• Range acceleration first checks that the source really honours byte ranges. If the source does not, Flux uses a complete stream rather than assuming that extra connections guarantee a faster or correct result.
• Use .flpm manifests to carry a prepared download list. Review imported sources before starting work; importing a list does not verify rights or make every source available.

Example: gather the inputs for a client document pack

1. Review the authorised links supplied for the task and identify the expected file from each source.
2. Add the batch, then inspect which links were accepted and which need correction. Resolve an access error at the source rather than repeatedly retrying it.
3. Wait for completion and inspect representative files. Compare expected size and contents where available before importing documents into FOLD.
4. Keep a simple record of which source belongs to each deliverable. A completed source transfer is an input, not proof that the final merged document is correct.

From downloads to a client handover

Recover progress and verify the completed file

Flux keeps owned queue records and the private data needed by its download engine. Restored range work is checked before assembly. A completed range download is published after its parts and assembled file are flushed, known byte counts agree and a SHA-256 digest is computed.

Open the actual output and confirm that it is the expected file. A webpage saved instead of a document can still contain bytes, and a familiar filename is not a content check. Signed sharing is a separate explicit action; keep its expiry and recipient needs in view. If a transfer is uncertain or failed, preserve the recorded reference and inspect the message before starting another copy.

Private storage, scheduling and clear measurements

Download records and private files belong to the verified Account owner. Shared delivery links have their own expiry rather than treating a bare download identifier as public authority. Scheduled UTC start times survive restarts, and due work rechecks current Account access before starting.

Displayed speed and activity describe measured or recorded transfer state. An idle queue does not imply an active stream; completed cloud bytes are not a promise of remaining storage capacity or network bandwidth. This deterministic transfer workflow does not use a paid AI generation model.

Questions about links and transfer behaviour

Flux walkthrough · Organise project downloads · Direct and cloud downloads · Build a clear handover