@deckflow/deckrender

DeckRender

Render any document format into visual artifacts.

DeckRender is a pure render engine. Give it a document, get back pixels — images, a PDF, or a video. Nothing else.

deckrender deck.pptx -o deck.png
deckrender deck.pptx -o deck.pdf
deckrender deck.pptx -o deck.mp4

It is to documents what ffmpeg is to media: one command, a small set of flags, predictable output. It deliberately does not parse content, extract text, or edit files — those belong to other tools in the DeckFlow family.

Install

npx -y @deckflow/deckrender@latest deck.pptx

npm install -g @deckflow/deckrender

Requires Node.js 18 or newer.

Quick start

Render every slide to PNG. With no -o, output lands in a directory named after the input:

$ deckrender presentation.pptx
presentation/

presentation/
├── 001.png
├── 002.png
└── 003.png

Pick a format, a size, and a page range:

deckrender report.pdf --pages 1-5 --width 2560 -o pages/
deckrender deck.pptx --format pdf -o deck.pdf
deckrender page.html -o screenshot.png
deckrender https://example.com -o screenshot.png
cat page.html | deckrender - --from html -o screenshot.png

Machine-readable output for scripts and agents:

$ deckrender deck.pptx --json
{
  "ok": true,
  "input": "deck.pptx",
  "format": "image",
  "engine": "cloud",
  "route": ["convertor.ppt2image"],
  "pages": 3,
  "outputs": [
    { "page": 1, "file": "presentation/001.png", "width": 1920, "height": 1080, "bytes": 184320 }
  ],
  "durationMs": 8123
}

Supported formats

deckrender formats

Input	→ image	→ pdf	→ video
.pptx .ppt	✅	✅	✅
.pdf	✅	✅	🕓
.key	✅	✅	🕓
.docx .doc	✅	✅	—
.xlsx	🕓	🕓	—
.pages	✅	✅	—
.numbers	✅	✅	—
.html + URLs	✅	✅	✅
.md	✅	—	—

Image output supports png, jpg and webp via --image-format.

🕓 is planned but not built; those report not_implemented with a message naming what is blocking them. Unsupported pairs fail with a clear message rather than producing something approximate.

Pages and Numbers render their embedded first-page preview — see docs/formats.md for that and the other per-format notes.

Full detail, including which flags each route accepts: docs/formats.md.

Authentication is optional

DeckRender works with no setup at all — rendering runs in guest mode. Log in when you want higher quotas or a private workspace:

deckrender auth login

Credentials are stored in ~/.deckflow/credentials and shared across every DeckFlow CLI. Log in once through DeckRender and DeckHTML picks it up too, and vice versa. If your machine already has DECKHTML_API_KEY set, or you have logged in with the deckops CLI, DeckRender uses that automatically.

deckrender config list    # shows every value and exactly where it came from

See docs/configuration.md for the full resolution order.

Use it as a library

The CLI and the programmatic API ship in the same package.

import { render } from '@deckflow/deckrender';

const result = await render({
  input: 'deck.pptx',
  format: 'image',
  pages: '1-10',
  out: 'frames/',
});

console.log(result.route); // ['convertor.ppt2image']
console.log(result.outputs); // [{ page: 1, file: 'frames/001.png', ... }]

Reuse configuration, or swap in your own render backend:

import { createRenderer, type RenderEngine } from '@deckflow/deckrender';

const renderer = createRenderer({
  apiKey: process.env.DECKFLOW_API_KEY,
  onWarning: (message) => console.warn(message),
});

Documentation

Quick start	Install and first render
CLI reference	Every command and flag
Formats	What converts to what, and the flags each route accepts
Profiles	Named flag presets
Configuration	Credentials, shared auth, render defaults
Errors	Error codes and exit codes
Roadmap	What is coming and what is blocked upstream

How it works

Input (file | URL | stdin)
   → InputResolver     normalize and classify
   → RenderPlan        route table: source × target → ordered backend tasks
   → RenderEngine      pluggable; v0.1 ships the cloud engine
   → ArtifactWriter    page selection, naming, files / directory / zip
   → Result            human text or --json

Rendering is performed by @deckops/sdk. DeckRender contributes the input model, the render routing, artifact naming, and a stable output contract.

Most rendering runs in the DeckFlow cloud; a few formats are handled on your machine. Which is which is an implementation detail — deckrender formats reports what works, and --json reports how it was produced if you need to know.

Development

Issues and pull requests are welcome. Node.js 18 or newer.

pnpm install
pnpm check                    # typecheck + lint + unit + integration
pnpm build && pnpm test:e2e   # e2e drives the built binary

DECKRENDER_E2E=1 pnpm test:cloud    # guest render against the live backend
pnpm test:conformance              # every format pair; needs credentials

The route table in src/core/routes.ts decides what converts to what. Probe the backend before adding to it — several plausible-looking conversions do not actually work, so a route inferred from type definitions alone can be wrong. pnpm test:conformance confirms the matrix end to end.

The --json envelope, error codes, exit codes and the shared credential file format are what other people's scripts depend on. Changing any of them is a breaking change; note it in CHANGELOG.md.

License

MIT © DeckFlow