A workbench, not a service.

split.tools exists because a simple job — cutting a file into pieces — somehow became a cloud service. To slice a photo for Instagram or pull three pages from a contract, the typical tool asks you to upload the file to a stranger's server, wait in a queue, accept a watermark, and trust a deletion promise.

None of that is technically necessary. Modern browsers can decode images, parse PDFs, analyze audio, and capture video on their own. So that's what this site does: splitters for PDFs (including by size and pages in half), CSV files, images, audio, video, and any file at the byte level — all running entirely on your device. There is no processing backend. Not a small one; none.

What that buys you

• Privacy by architecture.Files are never transmitted, so there is nothing to store, leak, or delete. You can verify this with your browser's network inspector — we encourage you to check.
• Speed.No upload, no queue, no render farm. A 2 GB video is ready to cut the moment you drop it.
• No strings. Free, no accounts, no watermarks, no file-size tiers. Local processing costs us nothing per file, so nothing needs to be metered.

Who builds it

split.tools is designed, built and written by Abdessamad Bettal, a software engineer who works on file formats and browser media APIs. Every guide in the cutting roomcomes from building these tools: the CSV splitter's quote handling, the PDF tools' page-box geometry, the byte-exact ZIP writer. When a guide makes a claim about a format, it's one the code had to get right.

How it's built

The site is a static Next.js app. Splitting runs on web platform APIs — canvas for images, pdf.js and pdf-lib for documents, Web Audio for sound, MediaRecorder for video, Blob slicing for CSV and byte-level splits — with a hand-rolled, streaming ZIP writer for batch downloads. The full technical tour is in this engineering post.

Questions, bug reports, or a tool you wish existed? Get in touch.