OFFICIAL CLI

Use NEXO from the command line with the same infrastructure as the product.

The official CLI sends conversions to the hosted NEXO API, keeping layout, free-mode limits, and usage counting centralized in the backend.

Open CLI repository Try Free in the browser

Global commandSame product APICLI origin in Supabase

CLI

Current CLI scope

The first CLI version focuses on markdown, optional logo, and a saved local default logo. Attachment-heavy workflows are still better handled in the web app.

1. Install globally

Use npm to make the command available on your machine. After that, running conversions stays simple for any markdown file.

Install

npm install -g nexo-md-to-pdf-cli

2. Convert one file or run in batch

Each `.md` becomes its own conversion job. That makes local automation, scripts, and CI routines easier without mixing files in the same command.

Usage

nexo release-summary.md

Batch

nexo a.md b.md --output-dir ./pdfs

3. Save a default logo once

If you always use the same brand asset, configure it once in the CLI. After that, plain `nexo file.md` conversions automatically reuse that branding by default.

Saved branding

nexo config set-logo ./brand.svg --logo-tone light

Config

nexo config show

Open CLI repository View guide in main repo

Scope

Same source of truth

Because the CLI uses nexo.speck-solutions.com.br/api/free/convert, usage keeps being counted in Supabase and the backend distinguishes WEBSITE and CLI.

Markdown conversion supported
One-off and saved default logos supported
Attachments out of scope for v1

Try Free in the browser