How to use OneKit.
Browser, workflows and CLI.

OneKit helps you compare, convert and process PDFs, images, documents, code and other files. Use a single tool for a quick task, connect tools for a repeated job, or run the shared Python core from your command line.

The catalog contains 285 tools; 255 currently run in the browser. Search by task or format, then use the category filters to narrow the list. Enable Show CLI tools to see operations available through the CLI with their required dependencies.

Thanks to advanced browser technology, OneKit processes your files directly on your device. Your documents and results stay with you, without being uploaded to our servers. OneKit downloads the processing environment and required packages, then reuses them as you move between tools.

1. Open a tool. Choose an operation from the catalog and check its input requirements.
2. Add your input. Select files or paste text where supported. Use Replace or Remove to change the selection.
3. Set the options. Choose the output format or settings. Supported PDF tools offer page previews and reordering; image cropping offers a visual selection.
4. Run and download. Wait for processing to finish, inspect any warnings, then download the result. Save it before refreshing or closing the page.

Combine tools across categories in a single workflow: convert a file, process its contents, then compress or package the result. Mix and repeat steps as needed, provided each tool accepts the output format and file count from the previous step. OneKit passes results between steps automatically, without downloading and choosing files in between.

Processing several files? Use a workflow. Choose a pool of files: single-file tools run in a For each file loop, applying the same settings to every input. Each pass sends its results to the next step. Tools such as Merge PDF process the group together, in the selected order. Comparisons and diffs are excluded because they require a specific pair of inputs.

1. Start with a file pool

   Choose one or more inputs and the first tool. Add, remove or reorder files before running.

2. Build your sequence

   Combine compatible tools from any category. Repeat steps and adjust their options.

3. Run and reuse

   Run the workflow, download your results and save the setup for next time.

Steps run in numbered order; moving blocks changes only their position. The pool supports up to 256 files and 128 MiB total; each step also keeps its own file size and total limits. A failure stops the workflow without publishing partial results. Download multiple results together as a ZIP. A saved .1kit setup preserves tools, options and layout, without input files or passwords.

You can also run a saved setup from the CLI:

onekit pipeline --steps workflow.1kit input.pdf -o output/

The CLI gives you direct access to the Open Source (PolyForm Shield 1.0.0) Python core at the heart of OneKit. Run all 285 tools, including those not yet available in the browser, with more generous file-size limits where supported. Everything runs on your machine.
Requires Python 3.11 or later. Limits vary by tool; some operations need optional packages or external engines such as FFmpeg, LibreOffice or Pandoc.

python -m pip install "onekit-tools[pdf,images,documents]"

Use OneKit directly or as a local toolkit for an AI agent that can execute shell commands. Your agent can discover tools, check requirements, process files and run saved .1kit workflows. File processing runs locally; what reaches a remote model depends on your agent configuration.

onekit list --json
onekit doctor pdf-merge --json

onekit run pdf-merge first.pdf second.pdf -o combined.pdf

For agent workflows, parse discovery and readiness JSON, pass explicit input/output paths and check the exit status before reading results. run and pipeline write output files; some tools produce JSON reports. Prepare dependencies before unattended runs, since first-use setup may need downloads or interaction. Use onekit doctor TOOL_ID to check the dependencies for a specific tool. OneKit preserves existing output files unless you deliberately pass --force. For passwords, use --ask-password to keep secrets out of shell arguments.

Help build OneKit's open revolution: everyday tools for everyone, from hands-on tasks to workflows run by local AI agents. Contribute to make tools more efficient and effective: improve speed and memory use, fix incorrect results, add regression examples, or clarify documentation and agent workflows. Read the contribution guide ↗

The OneKit Python core is Open Source (PolyForm Shield 1.0.0). Its code powers both the browser tools and the CLI. You can inspect the implementation, report a bug, suggest a tool or contribute a fix.

Help build OneKit's open revolution: everyday tools for everyone, from hands-on tasks to workflows run by local AI agents. Contribute to make tools more efficient and effective: improve speed and memory use, fix incorrect results, add regression examples, or clarify documentation and agent workflows. Read the contribution guide ↗

You may use, modify and redistribute the core for permitted purposes, including commercial and internal use. You may not use it to provide a product or service that competes with the software or with a product the licensor or its affiliates provides using the software; free offerings and different platforms or interfaces can also compete. When sharing copies, include the license text or its URL and any Required Notice lines supplied with the software. The full license governs, including its exceptions for new and discontinued products, patent terms and warranty disclaimer. Here, “Open Source (PolyForm Shield 1.0.0)” describes published source under these terms; the noncompete restriction means this is source-available software rather than unrestricted open source under the Open Source Definition.