AISeriesMaker

The plan limits behind an AI series

Luma and Pika: plan limits side by side

Luma and Pika publish their plan limits differently on 5 of the eight: generations at once, file keeping, seats, unused credits and extra credits. From 2 source pages, read 2026-09-25; no maker pays to be listed.

Limits each publishesSolid: published. Hollow: not on the pages read.Limits each publishesLumaPikaGenerations at onceGenerations at once — Luma: Not stated on the pages readGenerations at once — Pika: A number per planPriority and slow lanesPriority and slow lanes — Luma: A priority queue on some plansPriority and slow lanes — Pika: A priority queue on some plansStorage allowanceStorage allowance — Luma: Not stated on the pages readStorage allowance — Pika: Not stated on the pages readHow long files stayHow long files stay — Luma: Deleting is permanentHow long files stay — Pika: Not stated on the pages readSeats and collaboratorsSeats and collaborators — Luma: Collaborators invitedSeats and collaborators — Pika: Not stated on the pages readProject capsProject caps — Luma: Not stated on the pages readProject caps — Pika: Not stated on the pages readUnused plan creditsUnused plan credits — Luma: Not stated on the pages readUnused plan credits — Pika: Reset each cycleExtra creditsExtra credits — Luma: Not stated on the pages readExtra credits — Pika: Bought credits expire later
Fig. 1 Solid: published. Hollow: not on the pages read.
Luma and Pika, limit by limit, read 2026-09-25.
LimitLumaPika
Generations at onceNot stated on the pages readA number per plan
Priority and slow lanesA priority queue on some plansA priority queue on some plans
Storage allowanceNot stated on the pages readNot stated on the pages read
How long files stayDeleting is permanentNot stated on the pages read
Seats and collaboratorsCollaborators invitedNot stated on the pages read
Project capsNot stated on the pages readNot stated on the pages read
Unused plan creditsNot stated on the pages readReset each cycle
Extra creditsNot stated on the pages readBought credits expire later

Inclusion rule. The eight limits every tool on the sheet is read for. Order. The order limits take on every tool page.

1How the two compare

Luma publishes file keeping and seats, which Pika's pages leave out. Pika publishes generations at once, unused credits and extra credits, which Luma's pages leave out. Both publish queue lanes the same way: a priority queue on some plans. Neither publishes storage and project caps.

2The published wording where they differ

Seats and collaborators

Edit access for guest collaborators

Luma, pricing page

Pika publishes nothing on this limit.

Unused plan credits

Luma publishes nothing on this limit.

Plan credits refresh each billing period and do not roll over.

Pika, pricing page
  • Plus plan
    Edit access for guest collaboratorsLuma, pricing page / recorded 2026-09-25
  • Credits FAQ
    Plan credits refresh each billing period and do not roll overPika, pricing page / recorded 2026-09-25

3Luma and Pika against a third tool's published limits

SceneMixer's published figure on the limits where Luma and Pika differ, read 2026-09-25.
LimitSceneMixerSource
Generations at once3 at once on a free account; 5, 8, 10, 15 and 20 on the paid tiersSceneMixer, guide to what a paid plan changes
Unused plan creditsMembership credits land in the same balance as bought credits and do not expire at month endSceneMixer, guide to what a paid plan changes
Extra creditsCredit packs bought as needed, with no monthly feeSceneMixer, pricing page

Inclusion rule. Limits on which the two tools differ and SceneMixer publishes a figure or a rule. Order. The order limits take on every tool page.

4Other matchups with these tools