Skip to content
ForgePlug — Logo
pdf100% Browser-BasedNo SignupNo WatermarkUpdated Aug 2026

Bulk File Operations

The only genuinely free batch file processor on the web. Compress, convert, watermark, and merge PDFs. Convert, resize, compress, and strip EXIF metadata from images. Everything runs in your browser — no uploads, no paywalls, no artificial limits. Just honest processing power powered by your device.

Your Files Never Leave Your Device

All processing happens entirely in your browser. No uploads, no servers, no tracking.

1
2
3

What type of files are you working with?

Choose the file type to see available batch operations.

Supported Formats

Process a wide range of file types directly in your browser

PDF

Portable Document Format

JPEG

Joint Photographic Experts Group

PNG

Portable Network Graphics

WebP

WebP image format

AVIF

AV1 Image File Format

BMP

Bitmap image file

GIF

Graphics Interchange Format

Frequently Asked Questions

Everything you need to know about bulk file processing

Is there a limit on how many files I can process?
There is no artificial limit. The only constraint is your browser's memory. ForgePlug processes files in parallel streams and releases memory as each file completes, so you can handle hundreds of files. If your batch is large enough to risk browser instability (around 500 MB total on desktop), the tool will warn you and suggest splitting the batch — this is an honest technical limit, not a paywall.
Are my files uploaded to any server?
No, absolutely not. Every operation — PDF compression, image conversion, metadata stripping, everything — happens entirely in your browser using JavaScript. Your files are read from your device, processed locally, and never transmitted over the internet. This is the core privacy promise of ForgePlug.
What file formats are supported?
PDF operations accept .pdf files. Image operations accept .jpg, .jpeg, .png, .webp, .avif, .bmp, and .gif files. You can drop a folder of mixed formats and the tool will filter to only the files relevant to the chosen operation.
Can I process files on my phone?
Yes. The tool is fully responsive and works on mobile browsers. Mobile devices have tighter memory limits, so the tool uses a lower warning threshold (150 MB vs 500 MB on desktop) and recommends processing in smaller batches. All operations, including drag-to-reorder for PDF merging, work with touch.
What happens if one file in a batch is corrupted?
ForgePlug reports per-file failures without aborting the rest of the batch. A corrupted or unreadable file will be marked with an error status, and processing continues with the remaining files. You can see exactly which files succeeded and which failed in the results summary.
How does PDF-to-image conversion work?
ForgePlug uses Mozilla's pdf.js library to render each page of a PDF onto a canvas, then exports the canvas content as JPG or PNG. You can choose the output quality (for JPG) and the render scale (higher scale = higher resolution output). Each page becomes a separate image file.
Does stripping EXIF data actually remove GPS location?
Yes. When you strip EXIF metadata from a photo, the GPS coordinates, camera information, date/time, and all other embedded metadata are removed. The image content itself is not affected — the photo looks exactly the same, but it no longer contains any information about where or when it was taken. This is important for privacy when sharing photos online.
How do you handle file name collisions in the download?
When downloading processed files, ForgePlug adds descriptive suffixes (like -compressed, -converted, -resized) to the original file names. If two files would end up with the same output name, a number is appended to avoid collisions. The final ZIP contains clearly named files that are easy to identify.
Why is this tool free when others charge for batch processing?
Because ForgePlug runs entirely in your browser, there are no server costs for processing your files. Other tools charge because they run processing on their own servers and need to cover infrastructure costs — or more honestly, because batch processing is a profitable upsell. ForgePlug's browser-based architecture means processing is done on your device, not ours, so there is no infrastructure cost to pass on.
Does this work offline?
Yes, once the page has loaded. Every library this tool uses — pdf-lib, pdf.js, and the image processing code — is bundled with the page itself rather than fetched from a third-party CDN at the moment you use it, so all processing keeps working with no internet connection. You only need to be online to load the page the first time.

Batch File Processing: Why Browser-Based Matters

How processing files in your browser keeps your data private and avoids paywalls.

Most batch file processing tools online require you to upload your files to their servers, then pay for the privilege of processing more than a handful at a time. iLovePDF, SmallPDF, and Adobe Acrobat all cap free batch processing at one to three files — not because the technology requires it, but because that is their business model. ForgePlug's Bulk File Operations tool takes a fundamentally different approach: everything happens in your browser, on your device, with no server involved at all.

Why Browser-Based Processing Is Better

When you process files in the browser, your data never leaves your device. There is no upload, no temporary server storage, and no third party that can access your documents. This matters especially for sensitive files — business contracts, medical records, personal photographs with GPS data, or financial documents. Browser-based processing eliminates the privacy risk entirely.

The trade-off is that browser-based processing is limited by your device's memory and CPU. A server has gigabytes of RAM and multiple CPU cores dedicated to the task; your browser shares resources with tabs, extensions, and the operating system. ForgePlug's tool is engineered to work within these real constraints — processing files in parallel streams, releasing memory as each file completes, and warning you honestly when a batch is large enough to risk browser instability.

How ForgePlug Handles Large Batches

Instead of processing all files simultaneously (which would crash the browser with large batches), ForgePlug uses bounded concurrency: it processes 3 files at a time in Web Workers, releasing each file's memory immediately after processing completes. Output files are streamed into a ZIP archive incrementally rather than held in memory until the end. This means you can process hundreds of files without running out of memory — as long as individual files are reasonably sized.

When a batch's total size is large enough to genuinely risk a browser crash (typically around 500 MB on desktop or 150 MB on mobile), the tool warns you proactively and suggests splitting the batch. This is an honest technical limitation, not an artificial cap — if your device can handle it, the tool lets you proceed.

PDF Operations

Compress reduces PDF file size by re-encoding and optimizing the document structure. Choose from three quality presets to balance file size against visual fidelity. Merge combines multiple PDFs into one, with drag-to-reorder control over the final page sequence. Watermark applies a text or image watermark to every page of every PDF, with configurable position, opacity, and size. Convert renders each PDF page as a JPG or PNG image, useful for sharing PDF content on platforms that do not support PDF uploads.

Image Operations

Convert changes image formats between JPG, PNG, WebP, and AVIF without uploading to a server. Resize scales images by percentage or fixed dimensions, with aspect-ratio lock as default. Strip EXIF Data removes GPS location tags and other metadata — this matters for privacy because photos taken with smartphones embed your exact GPS coordinates, and sharing those photos without stripping EXIF data shares your location. Compress reduces image file size using the Canvas API's built-in compression.

Tool Overview

A closer look at Bulk File Operations — how it works, who it's for, and where it fits in your workflow.

Batch processing is the point at which most free file tools stop being free. Compressing one PDF is offered everywhere; compressing the forty PDFs sitting in a folder is the feature that sits behind a subscription. The technical reason usually given is server cost — and for a server-based tool that is true, because every file has to be uploaded, processed on someone else's hardware, and downloaded again. Doing the work in the browser removes that cost entirely, which is why batch mode here is not capped at three files to nudge you toward an upgrade.

Running in the browser changes the engineering problem rather than eliminating it. The constraint stops being server capacity and becomes your device's memory. Processing forty large scanned PDFs by loading all of them at once is a reliable way to crash a tab, so the work is deliberately bounded: files are processed a few at a time rather than all at once or strictly one after another, each result is added to the output archive as soon as it is finished rather than held in memory until the end, and a warning appears before you start if the batch is large enough to be genuinely risky — with a lower threshold on mobile, where memory ceilings are tighter.

The heavy work runs in Web Workers, off the main thread. This is the difference between a tab that stays responsive with a live per-file progress list and one that freezes for ninety seconds and looks crashed. Failures are isolated per file too: one corrupt or password-protected PDF in a batch of fifty is reported against that file and skipped, rather than aborting the run and losing the other forty-nine results.

Everything comes back as a single ZIP with predictable names — original filename plus an operation suffix, with a number appended if two outputs would otherwise collide. PDF operations cover compress, merge, watermark, and page-to-image conversion; image operations cover format conversion, resizing, EXIF stripping, and compression. No file is uploaded at any point.

Key Features

Everything you get with this tool, at a glance.

No artificial file limit

The only ceiling is your device's memory, not a plan tier — batch mode is not the upsell.

Web Worker processing

Heavy work runs off the main thread, so the page stays responsive with live per-file progress.

Bounded concurrency

Files process a few at a time — faster than sequential, without the memory spike of all at once.

Per-file failure isolation

A corrupt or locked file is reported and skipped instead of aborting the whole batch.

Streamed ZIP output

Each result is added to the archive as it finishes rather than held in memory until the end.

Nothing leaves the device

Every operation runs locally in the browser — no upload, no server copy, no retention window.

How to Use Bulk File Operations

Get from zero to done in four quick steps — no account, no learning curve.

  1. Pick a category and an operation

    Choose PDF or image first, then the specific operation. The available settings change per operation — compression exposes a quality preset, resize exposes dimensions and an aspect-ratio lock.

  2. Add files or a whole folder

    Drag files in, browse for them, or select an entire folder. Anything that does not match the chosen category is filtered out and reported rather than silently dropped.

  3. Heed the batch size warning

    If a warning appears about total size, it is a genuine memory estimate rather than a paywall prompt. Splitting the batch in half is more reliable than pushing through and risking a crashed tab.

  4. For merge, set the order before running

    Merge output follows the list order, so arrange files first. Use the arrows to move a file up or down; on touch devices the rows can be dragged directly.

  5. Review the per-file results

    The results list shows every output with its size, and any failures with the reason. Check it before downloading so a skipped file does not go unnoticed.

Practical Examples

Real input and output pairs so you know exactly what to expect.

Compress a folder of scans

Input

34 scanned PDFs, 180 MB total

Output

34 compressed PDFs in one ZIP, each named originalname-compressed.pdf

Strip GPS data before sharing photos

Input

60 JPEGs straight from a phone

Output

60 re-encoded images with all EXIF metadata removed, named originalname-no-exif.jpg

Convert a multi-page PDF to images

Input

One 12-page PDF, output set to JPG

Output

12 separate images named document-page-1.jpg through document-page-12.jpg

Was this tool helpful?

Your feedback helps us improve Bulk File Operations for everyone.

Share this tool

Share
Runs in your browser100% privateNo data uploaded