Omni Tools¶

Omni Tools is a self-hosted collection of powerful web-based tools for everyday tasks.

Description¶

It provides a wide array of utilities, including text tools, coding tools, and media tools, all accessible through a single web interface. It is designed to be lightweight and runs entirely in your browser without tracking or ads.

What it is¶

Omni Tools is a privacy-oriented browser toolbox for common transformations such as JSON formatting, image conversion, PDF operations, hash generation, text cleanup, and date/time conversion. The application is distributed as a static web app, so most day-to-day work happens in the user's browser rather than in a server-side processing queue.

What problem it solves¶

It replaces the habit of pasting sensitive snippets, screenshots, documents, or configuration fragments into random online utility sites. For a home office, this keeps small conversion jobs inside the LAN while giving non-technical users a simple web page instead of a collection of command-line scripts.

Where it fits in the stack¶

Omni Tools belongs in the self-hosted productivity utilities layer, next to IT-Tools and CyberChef. It is best exposed behind a private reverse proxy, SSO portal, or VPN for quick access from family or team devices.

Typical use cases¶

Format or validate JSON, CSV, XML, Markdown, and text snippets.
Convert images, videos, PDFs, and other local files without uploading them to third-party web tools.
Generate hashes, UUIDs, QR codes, passwords, date calculations, and developer helpers.
Provide a safe internal fallback when SaaS utility sites are blocked or untrusted.

Strengths¶

Low-friction deployment: A single lightweight container can serve the toolbox.
Privacy posture: File-oriented tools are designed for client-side processing, reducing server-side data exposure.
Broad utility coverage: One interface covers many small office and developer tasks.
No account dependency: Useful as an internal utility even when external SaaS accounts are unavailable.

Limitations¶

Not an automation engine: It is interactive; use n8n, scripts, or APIs for repeatable pipelines.
Browser resource limits: Very large media/PDF jobs can exhaust client memory.
No granular workflow permissions: Put it behind network-level or reverse-proxy access controls if sensitive users share the same instance.

When not to use it¶

Do not use Omni Tools as the authoritative system for audited document transformations, regulated file processing, or unattended batch jobs. Prefer CyberChef for reproducible transformation recipes and dedicated services such as Paperless-ngx, Stirling PDF, or ImageMagick-based scripts for repeatable server-side processing.

Getting started¶

Docker quick start¶

Run the published container on an internal port:

docker run -d \
  --name omni-tools \
  --restart unless-stopped \
  -p 8080:80 \
  iib0011/omni-tools:latest

Open http://localhost:8080, choose a tool such as JSON formatter, paste a small test object, and confirm the output is rendered locally.

Docker Compose example¶

services:
  omni-tools:
    image: iib0011/omni-tools:latest
    container_name: omni-tools
    restart: unless-stopped
    ports:
      - "8080:80"

Start it with:

docker compose up -d

CLI examples¶

Omni Tools itself is a web app rather than a CLI, but these commands cover the common operational tasks:

# Pull the latest image before a maintenance window
docker pull iib0011/omni-tools:latest

# Follow web server logs while testing reverse-proxy access
docker logs -f omni-tools

# Confirm the service returns an HTTP response locally
curl -I http://localhost:8080

API examples¶

Omni Tools does not expose a stable public automation API for transformations. Treat it as a browser UI and use health checks for operations:

curl -fsS http://localhost:8080 >/dev/null && echo "omni-tools is reachable"

For scripted transformations, use dedicated CLIs instead. For example, a local JSON formatting fallback can be:

printf '%s\n' '{"service":"omni-tools","reachable":true}' > input.json
python3 -m json.tool input.json > formatted.json
cat formatted.json

Troubleshooting¶

If the page does not load, confirm the container is running with docker ps --filter name=omni-tools and that port 8080 is not already in use.
If reverse proxy assets fail, verify the proxy forwards the original host and path without stripping static asset prefixes.
If large files crash a browser tab, retry with a smaller file or switch to a server-side CLI designed for that media type.