Use Luma’s Ray documentation to plan a scene and understand keyframes, then check the narrower app evidence before depending on those controls. Ray 2 has a documented provider identity; the retained Ray 1.5 card has an unresolved mapping and is not treated as a confirmed separate endpoint.
Editorial starting points, not a performance ranking. Check current app access before choosing a model.
Build a calm environmental shot
Luma documents a ray-2 text-to-video request, making a carefully bounded scene brief a practical starting point. Keep the action and camera movement simple so you can inspect motion and perspective rather than judging only the opening frame.
Tradeoff: The owner audit records a five-second app card, not complete proof of every direct API option. Longer examples or additional provider services do not establish the app’s effective limits.
The provider documents starting and ending image keyframes. This is useful when preparing a controlled creative brief, but only use the image-guided workflow if that input is actually supported in your current app session.
Tradeoff: The audit does not verify keyframe passthrough. If the needed control is absent, do not assume writing an image filename into the prompt supplies the media.
Official documentation describes the named model or gateway—not every feature available in this app.
Use the exact model parameter
Luma’s video documentation lists Ray 2 as ray-2 and Ray Flash 2 as ray-flash-2. Its generation examples specify model, prompt, resolution and duration, including a ray-2 example at 720p for five seconds. That example is not a family-wide maximum or evidence that the application exposes every field.
The direct API describes image keyframes using frame0 and frame1 objects with an image type and URL. Start-only, end-only and paired keyframes are separate request shapes. It also documents loop and aspect_ratio fields. Provider support does not establish app-side uploads, field forwarding or guaranteed preservation of the supplied stills.
Luma documents camera-motion concepts and extension using generation references. Its extension guidance is for completed videos generated through Luma, not unrestricted editing of any uploaded footage. Keep these capabilities separate from a simple text-to-video call and from a promise of exact camera geometry or seamless joins.
Every existing catalog entry for this provider is linked below. Status labels come from the individual website guides; catalog coverage is not a guarantee of current app access. Historical and snapshot pages remain references, not extra active models.
Original prompt examples, not generated-output demonstrations. They have not been generation-tested.
Workflow 1
Establish a location with restrained movement
Define one location and one clear camera move. Avoid a long sequence of actions that requires the model to invent several connected shots within a short result.
A quiet timber footbridge crosses a narrow stream in a mossy garden. Move the camera slowly forward toward the bridge while leaves stir lightly at the edges of the frame. Preserve the bridge rails, water direction and perspective. Use soft overcast light, one continuous shot and no people, signs, animals or sudden weather changes.
Check the result: Inspect rail connections, water flow and foreground edges throughout the shot. Confirm that the camera movement supports your edit and does not reveal impossible geometry.
Only use this workflow after confirming image input is available. Attach an authorized still and describe a small change; otherwise keep it as a production brief rather than pretending the app received the image.
Use the supplied still of a blue ceramic bowl on a linen table as the starting composition. Animate only the sheer curtain visible at the edge of the frame, with a slight natural movement in the soft daylight. Keep the bowl, linen folds, camera angle and colors unchanged. Add no hands, food, lettering or camera movement.
Check the result: Compare the first frame and several later frames with the still. Check whether the bowl and fabric stay stable instead of assuming an image-guided result is a faithful edit.
Official provider or gateway documentation supports the cited API capabilities. App mappings come from owner-supplied audits labeled October 9, 2026, not live generation tests. A listed model and a provider feature do not establish current app access or parameter forwarding.
Owner audit · October 9
Ray 2’s recorded app route
The audit identifies Luma’s direct API for the Ray 2 choice and a five-second card maximum. It does not show complete forwarding evidence for end keyframes, loops, camera concepts, resolution selection or audio-related services.
Owner audit · mapping conflict
Ray 1.5’s unresolved identity
The Ray 1.5 card records lumaModel = ray2. Its final handler request was not verified, so it may map to Ray 2 but that outcome is not asserted. The Ray 1.5 URL is retained with the conflict visible, not silently relabeled.
Documentation-only verification
What was not confirmed by this review
No generation established actual output length, native resolution, keyframe preservation, extension behavior or final-route identity. The current provider document listing Ray 2 does not by itself announce a Ray 1.5 retirement or resolve the owner’s configuration mismatch.
Before you rely on a result
Limits, costs and tradeoffs
An output described as high resolution may involve a separate upscaling workflow. Check the actual generation and delivery settings; do not infer native detail from a file’s final dimensions.
A camera-motion request is not a mechanical camera track. Check geometry, movement and transitions before using generated footage beside real video.
Do not attach a Ray 2 or Ray Flash 2 price to the unresolved Ray 1.5 card. The model identity, settings and serving contract must be established before any meaningful cost comparison.
Explore another prompt-led motion family with separate documented Standard and Pro hosting modes.
Common questions
Luma AI, without the assumptions
Is Ray 1.5 definitely serving Ray 2?
That is not confirmed. The owner audit records a ray2 configuration value for the Ray 1.5 card, but the final request was not inspected. The guide exposes the discrepancy without turning a possibility into a fact.
Can I extend any video using this app choice?
No such capability is established. Luma’s documented extension workflow has its own generation-reference requirements, and the app audit does not verify that this control is forwarded.
Does describing a final frame create a keyframe?
No. A text description is a creative request. Luma’s image keyframes are structured media inputs, and their availability in the app needs confirmation separately from the provider documentation.
Highlighted provider contracts reviewed . Individual model guides carry their own review dates. Sources can change; these pages do not perform live health checks.
Official provider or gateway documentation supports the cited API capabilities. App mappings come from owner-supplied audits labeled October 9, 2026, not live generation tests. A listed model and a provider feature do not establish current app access or parameter forwarding.