---
title: "Upscale video 2x (file paths)"
method: POST
path: "/v1/video/upscale/file"
tags: ["Image"]
---

# Upscale video 2x (file paths)

`POST /v1/video/upscale/file`

## Request

- Base URL: `http://localhost:9998`
- URL: `http://localhost:9998/v1/video/upscale/file`
- Auth: HTTP bearer

File-path variant of `/v1/video/upscale`. Accepts input and output file paths
instead of base64 data — no size limit beyond the 4096px dimension cap, no
base64 memory overhead. Designed for MCP tools and CLI integrations. Both
`input_path` and `output_path` are required. Returns metadata JSON with the
output path included.

## Request body

- object
  - `input_path` string, required: Absolute path to the input video file (MP4, MOV)
  - `output_path` string, required: Absolute path to save the upscaled MP4

## Response `200`

Upscale metadata with output path

- object
  - `input_width` integer
  - `input_height` integer
  - `output_width` integer
  - `output_height` integer
  - `total_frames` integer
  - `duration_seconds` number
  - `average_fps` number
  - `total_processing_seconds` number
  - `speed_ratio` number: processing_time / video_duration (>1 means slower than real-time)
  - `output_file_size_bytes` integer
  - `output_path` string

## Other responses

- `400`: Invalid request
- `429`: A video upscale is already in progress
- `503`: CoreML upscale service not available

---

[API](https://skmtc.dev/modelpiper/apis/toolpiper-api.md) · [All operations](https://skmtc.dev/modelpiper/apis/toolpiper-api/llms.txt) · [OpenAPI document](https://skmtc.dev/modelpiper/apis/toolpiper-api/revisions/6722bf56385c?raw)