Diwali 2026 five-day story series: one clip per day, Nov 6 to 10

Diwali 2026 runs five days from Dhanteras on 6 November to Bhai Dooj on 10 November. Make five 6-second stories from one music bed for about $1.88 on Sume.

5 min readSume
All posts

Diwali 2026 is a five-day festival from 6 to 10 November, so one greeting is not enough: you can post a different clip each day. A five-clip series, one still and one caption job per day on a shared music bed, costs about $1.88 on Sume's published rates and starts 34 days from 3 October.

The day-by-day list is from the 2026 table on Wikipedia's Diwali article, read 2026-10-03. Our existing Diwali greeting post covers a single greeting; this one covers the five-day sequence.

The five days and a clip for each

Wikipedia lists the observances below for 2026. Regional names differ, so pick the names your customers use and confirm them with someone from the community before you publish.

Diwali 2026 days per Wikipedia (read 2026-10-03) and a suggested clip
DateObservance (per Wikipedia)Clip idea
Fri 6 NovDhanterasGift or purchase of something new; show the item, a lamp, a price card
Sat 7 NovNaraka Chaturdashi / Chhoti DiwaliBehind the scenes; lamps being lit in the shop
Sun 8 NovLakshmi PujaThe main greeting; family or team portrait
Mon 9 NovGovardhan PujaCustomer thanks or a new-year offer
Tue 10 NovBhai DoojSibling gift idea; a gift-set still

What each day costs

Generate five 9:16 stills with bytedance-seed/seedream-4.5 ($0.05 each, so $0.25). Generate one music bed through the Music Router ($0.125, fixed per generation) and reuse its URL as the soundtrack of every day's render. Render each day as a 6-second Timeline job ($0.10 per ceil minute, so $0.10 each, $0.50 for five). Burn a short line with a caption job ($0.20 each, $1.00 for five).

The total is 0.25 + 0.125 + 0.50 + 1.00 = $1.875. If you skip captions on two days and put the line in the still instead, the total falls to $1.475.

Render order and idempotency

Submit the five Timeline jobs on 2 or 3 November rather than the night before. Each write needs an Idempotency-Key; reuse a key only when retrying the same body. Then post one a day. Because every render is a separate job, a redo for Sunday does not touch Friday's file.

import os, sys, uuid, requests

def main():
    key = os.environ.get("SUME_API_KEY", "")
    if not key:
        sys.exit("Set SUME_API_KEY first")
    body = {
        "video_url": "https://media.sume.com/artifacts/YOUR_ARTIFACT/clean.mp4",
        "style": "slam",
        "cues": [
            {"text": "Happy Diwali", "start": 0.5, "end": 4.5},
        ],
    }
    resp = requests.post(
        "https://api.sume.com/v1/video-captions",
        json=body,
        timeout=60,
        headers={"Authorization": "Bearer " + key,
                 "Idempotency-Key": str(uuid.uuid4())},
    )
    print(resp.status_code, resp.json())

if __name__ == "__main__":
    main()

What Sume does and does not do

  • Does: produce the stills, the bed, the five MP4s and the caption burn.
  • Does not: publish to social platforms or pick posting times.
  • Does not: know which observance your audience keeps. The names above are Wikipedia's; check them locally.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume