Can Deliteful handle large ZIP artifacts from CI/CD pipelines?

Yes. Individual ZIP files can be up to 50 MB, with batches up to 50 files or 2 GB total. Extracted output is capped at 5 GB per task. Most build artifacts fall well within these limits.

How does Deliteful prevent path traversal in ZIP contents?

Every file path inside the archive is validated before extraction. Entries containing '../' or absolute path references are rejected outright, so no file can be written outside its isolated extraction directory.

Does extraction happen on my infrastructure?

No. All extraction runs on Deliteful's isolated server environment. Your build agents and jump hosts are never exposed to archive contents.

What is the decompression bomb protection limit?

Total extracted output is capped at 5 GB per task. Archives that would exceed this limit are skipped automatically rather than partially extracted.

Extract ZIP Build Artifacts Without Local Risk

DevOps engineers regularly handle ZIP-packaged deployment artifacts, log archives, and infrastructure state exports — often from untrusted pipeline sources. Deliteful extracts these archives in an isolated server environment with hard decompression limits and path traversal prevention, eliminating the risk of running unverified ZIP content on a privileged build machine.

Create free account

When a pipeline produces a ZIP artifact from an external source, executing 'unzip' directly on a build agent or jump host carries real risk. A malformed archive with path traversal entries could overwrite configuration files or binaries in adjacent directories. A zip bomb could exhaust disk and stall downstream pipeline stages. Routing extraction through Deliteful moves that risk entirely off your infrastructure.

Deliteful caps extracted output at 5 GB per task and validates every file path before writing. The original folder structure inside the ZIP is preserved. Corrupted archives are skipped without failing the whole batch. Extracted files are returned for download via a secure link — no agent disk space consumed, no local tooling required.

How it works

1
Upload the ZIP artifact
Upload up to 50 ZIP files or 2 GB per batch — whichever limit is hit first.
2
Server-side safety validation
Deliteful verifies archive integrity and blocks path traversal entries before extraction begins.
3
Download clean extracted output
Receive your files in their original folder structure via a secure download link.

Frequently asked questions

Can Deliteful handle large ZIP artifacts from CI/CD pipelines?: Yes. Individual ZIP files can be up to 50 MB, with batches up to 50 files or 2 GB total. Extracted output is capped at 5 GB per task. Most build artifacts fall well within these limits.
How does Deliteful prevent path traversal in ZIP contents?: Every file path inside the archive is validated before extraction. Entries containing '../' or absolute path references are rejected outright, so no file can be written outside its isolated extraction directory.
Does extraction happen on my infrastructure?: No. All extraction runs on Deliteful's isolated server environment. Your build agents and jump hosts are never exposed to archive contents.
What is the decompression bomb protection limit?: Total extracted output is capped at 5 GB per task. Archives that would exceed this limit are skipped automatically rather than partially extracted.