JSON2Video 4K costs 4x the credits; Sume Timeline sizes and rate
JSON2Video charges 1 credit per second, 4 for 4K. Sume's Timeline bills $0.10 per output minute and takes edges from 256 to 2160, so no 3840-pixel width.

JSON2Video's pricing page charges 1 credit per second of rendered video, and 4K output costs 4 times the credits; its $49.95 pack holds 7,200 credits. Sume's Timeline has no resolution tier: it bills $0.10 per output minute, rounded up, and it accepts output widths and heights from 256 to 2160, so a 3840-pixel edge is not a Timeline output.
JSON2Video facts are from its pricing page, read 2026-10-01. Sume facts are from the Timeline docs. The vendor page also states an approximate per-minute range that does not reconcile with its credit rule, so this post uses only the credit rule.
How many seconds does 7,200 credits buy?
At 1 credit per second, 7,200 credits is 7,200 seconds, or 2 hours. At the 4x rate for 4K it is 1,800 seconds, or 30 minutes. That is the whole effect of the multiplier: the same pack renders a quarter as much 4K.
| Output | Credits per second | Seconds in 7,200 credits | Minutes |
|---|---|---|---|
| Standard resolution | 1 | 7,200 | 120 |
| 4K | 4 | 1,800 | 30 |
What does the same 2 hours cost on Sume?
If each output is one minute or less per render and you render 120 of them, Timeline is 120 minutes at $0.10, which is $12.00 before the 5.5% agent fee. If you render one 120-minute output, note that a single render is limited to 1,800 seconds of audio, so it must be split into at least four outputs.
Can Sume render 4K?
Not as 3840x2160. output.width and output.height take even integers from 256 to 2160, so 2160x2160 and 1080x1920 are valid and 3840x2160 is not. If you need a larger frame, generate or upscale it separately: image and video upscale are their own rate-card items. The default Timeline output is 1080x1920.
How do I know what a Timeline will cost?
POST /v1/timeline-1.0/plan is an unbilled preflight that returns billable_minutes and an estimate. It does not reserve credits or fetch media.
Sources
Related posts
More in Pricing
- LTX API pricing SKUs vs Sume's pricing_skus catalog field
An LTX SKU joins endpoint, model, resolution and output type, read from /pricing. Sume lists pricing_skus per video model in its catalog, at list x 1.25.
- Luma Agents usage: Pro 4x, Ultra 15x, and Sume Agent by plan
Luma lists 4x Luma Agents usage on Pro and 15x on Ultra. Sume gates Sume Agent by plan (limited on Free, full on Pro) and draws it from one credit balance.
- Kling 3.0 4K on Luma: 147 credits per second, audio on or off
Luma lists Kling 3.0 at 2160p for 147 credits per second with or without audio; at 1080p it is 40 without and 49 with. Sume has a generate_audio field.
- MiniMax H3 Max on Luma: credits per second in dollars
Luma lists MiniMax H3 Max at 18, 28 and 56 credits per second. Here is that in dollars by plan, and the per-second dollar rate Sume bills instead.
Written by Sume