Where your files are processed

Depending on the task, Daproc may process files entirely in your browser or upload them securely to our servers. Here’s how those options differ.

In your browser

Runs locally on your device

  • Processing runs in your browser.
  • Source files are not sent to Daproc servers.
  • Handy for smaller files: no waiting to upload to a server—the result appears right in your browser.
  • In-browser mode is indicated by an icon in the run button on the operation page.

On the server

Processing on Daproc servers

  • Files are uploaded over HTTPS and processed on the server.
  • Server-side processing is used for complex operations and large files that your browser or device cannot complete due to their limitations.
  • Files on the server are kept for 1 hour for download, then deleted automatically.
  • Files are used only to carry out your operations and are not shared with third parties for other purposes.
  • Server mode is indicated by an icon in the run button on the operation page.

More on data handling inPrivacy Policy

File Operations

Convert

What it does

Transforms a file from one type to another while preserving data structure as supported by the selected operation.

When to use

  • When a file must be opened in another tool.
  • When a team or client requires one standard format.
  • When a file should be prepared for the next pipeline step.

How it works

  1. Select a conversion operation.
  2. Upload the source file and start processing.
  3. Download the output in the target type.
  4. Check before run: the target type matches your next workflow step.

Merge

What it does

Combines multiple files into a single output with a consistent data structure.

When to use

  • When multiple files should become one final document.
  • When data comes in parts but must be handled as one version.
  • When one deliverable is easier to share and store.

How it works

  1. Select a merge operation.
  2. Upload all files that should become one output.
  3. Set file order if needed, then start processing.
  4. Check before run: file list is complete and order matches expected structure.

Split

What it does

Splits one file into smaller parts for staged processing, storage, or sharing.

When to use

  • When a large file should be delivered in smaller pieces.
  • When data should be split for parallel processing.
  • When separate fragments should be distributed to users.

How it works

  1. Select a split operation.
  2. Upload the source file.
  3. Set the split rule and start processing.
  4. Check before run: split rule matches your intended usage.

Edit

What it does

Changes file structure or content without extra manual steps.

When to use

  • When precise edits are needed without manual file recreation.
  • When documents should follow one structural standard.
  • When repeated edits must stay consistent over time.

How it works

  1. Select an editing operation.
  2. Upload the source file and configure required changes.
  3. Start processing and download the updated file.
  4. Check before run: edit parameters match the expected final result.

Extract

What it does

Extracts required data from source content into a form that is easier to use downstream.

When to use

  • When only relevant data should be extracted from source content.
  • When data should be prepared for analytics or import.
  • When repeated extraction must be automated.

How it works

  1. Select an extraction operation.
  2. Upload the source file and specify which data should be extracted.
  3. Start processing and download the extracted result.
  4. Check before run: selected data is exactly what downstream steps require.

Compress

What it does

Reduces file size while preserving a working output format.

When to use

  • When file size must be reduced before sending.
  • When target systems enforce strict upload limits.
  • When transfer speed and traffic usage matter.

How it works

  1. Select a compression operation.
  2. Upload the file for size optimization.
  3. Start processing and download the compressed output.
  4. Check before run: current size/quality balance is acceptable for your use case.