Skip to main content
The Human Bit
Ask Bit

GuidesChoosing a modelAnyone working with photos, screenshots, audio or video, not just text

When you need a tool that can actually see or hear

For Anyone working with photos, screenshots, audio or video, not just text.

Text only tools cannot read a photo, listen to a voice note or watch a clip. Choosing a tool that handles the kind of file you actually have saves a step and avoids a flat refusal.

When to use this

You have a screenshot, a photo of a whiteboard, a voice memo or a short video, and typing it all out yourself feels like the wrong way to spend the next twenty minutes.

  • Reads text and describes layout from a photo or screenshot
  • Transcribes and summarises spoken audio from a recording
  • Describes what is happening in a short video, frame by frame if asked

Workflow

  1. Check whether your file is text, an image, audio or video, and pick a tool built to handle that type

  2. Upload the actual file rather than describing it in words when detail matters

  3. Ask a specific question about the file rather than a vague one

  4. Ask the tool to flag anything it is unsure it read or heard correctly

  5. Confirm the important details yourself, especially numbers, names and quotes

Prompts to try

Use it, adapt it, and make it your own.

I am sharing [a photo, a recording, or a short video]. Please [describe, transcribe, or summarise] it, and tell me clearly if any part is unclear or hard to make out rather than guessing.
Ask Bit to adapt it →

Human lens

  • You judge whether what the tool read from the image or audio is actually correct
  • You provide the context the tool cannot see, like tone of voice or what happened just before the clip
  • You decide whether sharing that photo, recording or video with a tool is appropriate at all

What to avoid

  • Handwriting, poor lighting or background noise can lead to confident but wrong readings
  • A tool describing an image is not the same as verifying what is actually true in it
  • Sending photos or recordings of other people raises consent questions text alone does not

Related guides

View all →

When to spend more thinking, and when not to

Most tools now let you choose a faster answer or a slower, more careful one. Matching the effort to the task saves time and avoids polished but wrong answers.

Feeding in a whole document versus asking a short question

Some tools are built to hold a large document in view and reason across all of it. Others are better suited to a short, focused question. Picking the wrong one either wastes time or loses important detail.

Using a light tool for volume, and a stronger one for the hard cases

Not every task needs the strongest available model. Saving the most capable option for the tasks that truly need it keeps things fast and sustainable for everything else.

Recognising when a smaller model already does the job

For a lot of everyday writing, formatting and simple lookups, a smaller or lighter model gets you the same result faster. Knowing when that is true saves time without costing quality.

Tools that fit: Gemini, ChatGPT, Claude, Grok · Reviewed 2026-07-19