Guide · Open source
How to use omni-tools: Docker setup and tool overview
Updated · written with AI from the project's own documentation and checked against our catalogue data
omni-tools is a self-hosted web app that bundles many small utilities for everyday tasks, including PDF, image, text, date, math, and data tools. This guide shows you how to run it with Docker, find the tools you need, and understand how it processes your files. By the end you will have a working copy running in your browser on port 8080.
Quick start
- 1Install Docker. Make sure Docker is installed and running on the host machine. Docker is the only prerequisite listed for this install method.
- 2Run the container. Paste the docker run command from the README into a terminal. It pulls iib0011/omni-tools:latest and starts it on port 8080.
- 3Open the app. Visit http://localhost:8080 in your browser. Replace localhost with the server address if you are hosting it elsewhere.
- 4Pick a tool. Browse the categories such as PDF, image, text, date, math, and data, then open the tool you need.
- 5Process your files. Load your file into the tool. According to the README, processing happens on the client side, so the file stays on your device.
- 6Manage the container. Use Docker to stop or restart the omni-tools container when needed. The restart policy keeps it running after reboots unless you stop it.
What you need before you start
The only prerequisite listed in the project's install instructions is Docker. You do not need to install Node.js or clone the source code to run the app.
The README says the Docker image is about 28MB, which keeps downloads and deployment quick.
- Docker installed and running on the machine that will host omni-tools
Start omni-tools with a single Docker command
Run the following command to download the latest image and start it in the background. It maps port 8080 on your machine to port 80 inside the container, and restarts automatically unless you stop it.
When the container is running, open http://localhost:8080 in your browser. If you run it on another machine, replace localhost with that machine's address.
- -d runs the container in the background
- --name omni-tools names the container
- --restart unless-stopped restarts it after reboots unless you stop it manually
- -p 8080:80 maps host port 8080 to container port 80
docker run -d --name omni-tools --restart unless-stopped -p 8080:80 iib0011/omni-tools:latestRun omni-tools with Docker Compose instead
If you prefer a configuration file, the README provides a Docker Compose example using the same image and port mapping. Save it as a compose file and start it from the directory that contains it.
services:
omni-tools:
image: iib0011/omni-tools:latest
container_name: omni-tools
restart: unless-stopped
ports:
- "8080:80"Find the right tool by category
The README groups the tools into categories. The list is not complete, and the project says more tools are planned. Use the categories below to know what to look for.
- Image, video and audio: Image Resizer, Image Converter, Image Editor, Video Trimmer, Video Reverser
- PDF: PDF Splitter, PDF Merger, PDF Editor
- Text and lists: Case Converters, List Shuffler, Text Formatters
- Date and time: Date Calculators, Time Zone Converters
- Math: Generate Prime Numbers, calculate voltage, current or resistance
- Data: JSON Tools, CSV Tools, XML Tools
Understand where your files are processed
According to the README, all files are processed entirely on the client side, so nothing leaves your device. This is the main reason to choose omni-tools over ad-filled third-party sites when you work with private documents.
Because processing happens in the browser, the tools depend on your device's resources. The README does not describe server-side processing, so do not expect it to handle very heavy jobs that a server-based tool would manage.
Optional: run the project from source for development
Developers can clone the repository and run it locally. The project is built with React, TypeScript and Material UI. The README lists these commands for setup and for creating a new tool. Tests are run with npm as well.
git clone https://github.com/iib0011/omni-tools.git
cd omni-tools
npm i
npm run devWhat people use it for
- Splitting or merging PDF files without uploading them to a third-party site
- Converting or resizing images in a shared internal toolbox
- Formatting text and shuffling lists for everyday work
- Checking and converting JSON, CSV or XML during development
- Calculating date differences or converting time zones
Frequently asked questions
Is omni-tools free to use?
The project is released under the MIT License, as stated in the README and the repository metadata. The license file is in the repository, and you can read it for the full terms.
What do I need to install omni-tools?
The install method in the README requires Docker only. Run the single docker run command from the README, then open port 8080 in your browser.
Does omni-tools upload my files to a server?
According to the README, all files are processed entirely on the client side, so nothing leaves your device. Processing depends on your browser and device, not a server.
How do I fix a port conflict when starting omni-tools?
The README maps host port 8080 to container port 80. If 8080 is already in use, change the left side of the -p mapping to another free port and open that port in your browser instead.
How does omni-tools compare to IT-Tools, CyberChef, and Stirling-PDF?
The source does not compare these projects in detail. Omni-tools bundles a broad mix of everyday utilities, while the other projects are listed as comparable options; check their own documentation for specifics.
Can I host omni-tools for my team?
The README lists teams hosting an internal toolbox with a simple Docker command as a good fit. Use the same docker run or Docker Compose setup on a shared server.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
omni-tools suits people who want common file, text, and data utilities in one self-hosted place, especially if they want files processed in the browser. It is a poor fit if you need heavy server-side processing, or a tool outside the listed categories, or if you want zero setup and have no one to host it for you.
Install options & downloads