Batch Import Is Free, and Hard Limits Are Gone

Today we are shipping two changes together: batch import is now available in the free web app, and we removed the old hard caps that used to block larger jobs.

If you process files every day, this means fewer restarts, fewer artificial walls, and less time splitting work into tiny chunks.

The Update in One Line

• Batch import is now part of the free browser experience.
• No application-level upload or page caps are enforced.
• Practical limits are now based on your own device and browser resources.

The real limit should be your machine, not an arbitrary paywall.

What “Batch Import Is Free” Means

You can now drop multiple files, run one operation, and export all outputs in one pass across major workflows.

In practice:

1. Open a tool.
2. Add multiple files at once.
3. Apply settings once.
4. Download the full result (single output, ZIP bundle, or summary export depending on the tool).

You can test this right now in tools like Compress PDF, Image Converter, File Checksum Calculator, and QR Code Reader.

What We Mean by “Hard Limits Are Gone”

We removed fixed, application-level caps that previously blocked some workflows.

That does not mean infinite processing. It means constraints are now technical instead of arbitrary:

• Available RAM on your device
• Browser tab memory budget
• CPU speed and thermal throttling
• File complexity (for example, giant PDFs or very large images)

This is a more honest model: if your machine can handle it, VaultTools should not block it first.

Batch Workflows You Can Run Now

Here are common jobs that are now smoother:

• Compress many PDFs in one run for portal submissions
• Convert large image sets to one target format
• Extract checksum reports for multiple files and export CSV/JSON
• Decode many QR screenshots in one pass

For category-level entry points, go to PDF Tools, Image Tools, File Tools, and Developer Tools.

Practical Tips for Large Batches

For heavy jobs, a few habits improve stability:

1. Start with a medium batch first (for example 20-50 files) to estimate runtime.
2. Close memory-heavy tabs before launching very large operations.
3. Split extreme workloads into multiple batches if your browser becomes unstable.
4. Prefer ZIP exports for multi-file outputs so transfer and storage stay organized.

Privacy Model: Unchanged

This release does not change our core architecture.

Processing still runs locally in your browser with WebAssembly. Your files stay on your machine during transforms, and you export results directly from your own session.

Why We Shipped It This Way

VaultTools should feel like a real workstation in the browser, not a teaser funnel.

Batch import and limit removal are part of the same direction: remove friction for legitimate work while keeping the product free and privacy-first.

If you want details on how the free model works, see How It Stays Free.

Try It

Pick one repetitive task you normally do file-by-file and run it as a batch today.

That single change is where most users get the immediate time savings.