---
title: "CLI: The Whole API in Your Terminal"
description: "The official EnConvert CLI. Convert files between 40+ formats, render any URL or whole site to PDF, screenshot, or Markdown, and run the v2 web-data commands from one terminal command. Open source, MIT, zero telemetry."
canonical: "https://www.enconvert.com/integrations/cli"
locale: "en"
---

Official CLI · Open source

# The whole EnConvert API, one command in your terminal.

Convert files between 40+ formats, render any URL or whole site to PDF, screenshot, or Markdown, and run the v2 web-data commands, all from a single binary. JSON output, a built-in jq filter, and stable exit codes make it at home in scripts and CI.

brew install enconvert/tap/enconvert

Copy

Install

## Four ways in, same binary.

Pick the channel your machine already trusts. Every channel ships the same binary for macOS, Linux, and Windows.

### Homebrew

macOS and Linux. The tap tracks every release.

brew install enconvert/tap/enconvert

Copy

### Install script

One line on any Unix machine. The script detects your platform and installs the right binary.

curl -fsSL https://get.enconvert.com/install.sh | sh

Copy

### Scoop

Windows. Adds our bucket, then installs.

scoop bucket add enconvert https://github.com/enconvert/scoop-bucket && scoop install enconvert

Copy

### npm

Wherever Node already lives, including CI images.

npm i -g @enconvert/cli

Copy

Commands

## Everything the API does, verb for verb.

One binary covers the whole surface. If the API can do it, the CLI has a command for it.

1.  01

    ### Convert files

    Documents, images, and data files between 40+ formats. Point it at a file, name the target format, get the output path back.

2.  02

    ### Render any URL

    Turn a page into a PDF, a full-page screenshot, or clean Markdown with one command, rendered in a real browser.

3.  03

    ### Crawl whole sites

    Render an entire website to PDF, screenshots, or Markdown in one run instead of scripting a page-by-page loop.

4.  04

    ### Web-data commands

    The v2 verbs are first-class subcommands: perceive, discover, lookup, distill, and ingest, straight from the terminal.

5.  05

    ### api passthrough

    A gh-style escape hatch: enconvert api reaches every endpoint, including ones the CLI has no verb for yet.

6.  06

    ### Built for scripts

    \--json on every command with a built-in --jq filter, stable exit codes, --wait for long jobs, and shell completions for bash, zsh, and fish.

7.  07

    ### Profiles

    Keep separate keys and defaults per project or environment and switch with one flag.

In practice

## A few commands, end to end.

Real invocations, real output paths. Every command also takes --json when a script is the caller.

```
$enconvert convert quarterly-report.docx --to pdf-> quarterly-report.pdf$enconvert render https://example.com/pricing --to screenshot-> example.com-pricing.png$enconvert perceive https://news.example.com --json --jq .render_quality0.97$enconvert ingest https://docs.example.com --wait-> docs.example.com.chunks.jsonl
```

## MIT-licensed. Zero telemetry.

The CLI is open source under the MIT license, so you can read every line before you trust it with a key. It phones home to exactly one place: the EnConvert API you asked it to call. No usage analytics, no update pings, nothing else.

[

Source on GitHub

](https://github.com/enconvert/cli)

## CLI questions

What is the EnConvert CLI?

The official command-line interface for the whole EnConvert API in a single binary named enconvert. It converts files between 40+ formats, renders any URL or whole website to PDF, screenshot, or Markdown, and runs the v2 web-data commands: perceive, discover, lookup, distill, and ingest.

How do I install it?

Four channels, same binary: brew install enconvert/tap/enconvert on macOS and Linux, a one-line install script via curl on any Unix machine, Scoop on Windows, or npm i -g @enconvert/cli wherever Node runs. Shell completions for bash, zsh, and fish ship with it.

Do I need an API key?

Yes. The CLI runs against your EnConvert quota, so it needs an API key from your dashboard. A free account includes a monthly allowance while in beta, no credit card. Profiles let you keep separate keys per project.

What can it convert?

Documents, images, and data files across 40+ formats: PDF, DOCX, XLSX, PPTX, HEIC, WebP, CSV, and more. Beyond files, it renders live URLs and whole sites to PDF, screenshot, or Markdown in the same command grammar.

Is it open source?

Yes, MIT-licensed and public on GitHub, and it collects zero telemetry. The only network traffic it produces is the API calls you ask for.

How is it different from the MCP server and the SDK?

Same API, three doors. The MCP server plugs the API into AI agents like Claude and Cursor, the Node SDK is for your application code, and the CLI is for you: a terminal, a script, a CI job. Pick per surface, mix freely; they share keys and quota.

## One install away from your terminal.

The docs cover every command, flag, and exit code.

[Read the CLI docs](/docs/guides/integrations/cli.md)[

Star on GitHub

](https://github.com/enconvert/cli)