Skip to main content
Text & code prompt
Gemini
Gemini 4 Argon

Plan Foley From a Silent Visual Reference

Make an editor-ready sound cue sheet from a permitted silent clip or timestamped frames. Label proposed sounds, timing uncertainty and the frame that should anchor each cue.

By Genius Forges EditorialUpdated Oct 27, 2026

Use your attachments

Attach your files in the chosen AI platform, then paste this prompt.

Before you paste

Attach your own short silent clip in a supported Gemini interface, or provide approved still frames labeled with timestamps. The website itself does not receive the attachment.

Your prompt

Use the attached permitted silent clip, or labeled still frames with known timestamps, as the visual source. First list only visible actions with approximate start/end times and source frames. Then propose restrained Foley in a separate table: event | visual timing | suggested sound | alignment frame | uncertainty | audio rights/source to obtain. Do not claim to hear audio that was not supplied, invent unseen events or infer a real room’s acoustics. Distinguish contact visible on screen from contact that is obscured. Keep ambience separate from event cues. End with a manual timeline-alignment checklist. If the input cannot be read, ask for accessible frames rather than guessing.

Copy, paste, and create. Outputs can vary by model and settings.

Get one tested prompt a week

One workflow, one prompt, one tool and one quality check by email. No spam, unsubscribe any time.

Example result

Illustrative example; not tested on the listed platform. Synthetic visual observations for this illustrative preview: 0–2s: hand moves a cup toward a wooden table. Around 2.3s: cup base visibly meets the table. 2.3–4s: hand withdraws. Proposed cue: soft ceramic-on-wood tap at the visible contact frame; exact alignment requires editor review. Ambience: optional restrained room tone, separately sourced. No detected audio is claimed.

Illustrative example; not tested on the listed platform. Fictional or synthetic inputs are identified in the example.

How to use this prompt

  1. 1Attach the visual reference in a supported platform.
  2. 2Review the visible event list before accepting proposed sounds.
  3. 3Align the chosen authorized sound to the actual contact frame in your editor.

Tips & limitations

Check the result: 1. Observation and suggestion are separate. 2. Timing uncertainty is visible. 3. Every final sound has a permitted source. This is a text cue sheet, not generated audio or a verified soundtrack.

Did this help you complete your task?

Tell us what needs improving. No account or private output required.

Was this useful?
Report incorrect information or a broken link

Review evidence

Documentation-based review · 2026-10-27

Primary documentation and demo source reviewed on 27 October 2026. Exercises and expected results are illustrative unless an actual test is explicitly recorded. Local editorial review only; no provider-performance or audience outcome is claimed.

Keep creating

Explore the library
Gemini

Turn this idea into a daily skill

Practice with a small input and check the result before sharing.

We use optional cookies for analytics and referral tracking. Learn more about our privacy policy