File Names for Screen-Reading Tools

When an AI tool looks at your screen, it often reads what a person would see: thumbnails, window titles and the text next to files. In a file browser, a chat app or a web page, the file name is often the only readable label beside a thumbnail. A clear name gives the tool text it can quote and match. A cryptic name leaves it with a picture and little else.

Chris Hamilton, founder of Prisma, puts it this way: “If the AI has a good file name, the context when OCR reads the image also makes more sense.”

This is about OCR and screen-reading image search, not about how a library indexes files in the background. For that side of the story, see the guide on file names for search tools. The examples use a fictional client, ACM.

Who owns what

Someone has to keep the pattern readable on screen, not only on disk.

• Naming lead (studio level): keeps the written naming pattern short enough to read in a narrow column or a chat preview. Approves changes to field order.

• Project owner (per job): checks that review and delivery folders show clear names before anyone shares a screen or drops files into a chat.

• Everyone else: names files when they save them, rather than renaming only for a screenshot.

Folder and role names are examples; adapt them to your team.

Day-to-day workflows

Screen-reading tools see whatever is on the display. A few habits help:

1. Name before you show. Rename (or save with the studio pattern) before you share a folder window, a review board or a chat thread with thumbnails.

2. Keep the useful words visible. Put the client or project code and the asset description near the front of the name, so they still show when a column is narrow.

3. Spell out what a thumbnail can’t. A still of a logo and a still of a poster can look alike. ACM_logo-primary_v02.png and ACM_KV01_poster-a3_v01.png give the tool (and a teammate) different words to work with.

4. One pattern in every place files appear. The same name in the project folder, the review folder and the chat attachment, so a tool quoting the label can be checked against the real file.

5. Don’t rely on the thumbnail alone. If you ask a tool about “the blue one,” and the file is still called export (3).png, the screen may not give it enough text to be useful.

From intake to a shareable view

1. Intake. Client files land in 00_In/ with their original names, unless your client agreement says otherwise.

2. Work. As soon as a file enters your pipeline, save a copy with the studio pattern in 01_Project/ or 02_Assets/.

3. Review. Exports for review go into 05_Review/ already named. That is the folder people screen-share.

4. Chat or web handoff. Attach or upload the named file. Avoid a second, shorter nickname that only exists in the message.

5. Deliver. Approved files in 04_Out/ keep the same codes a screen-reading tool may have quoted earlier in the job.

Handoffs

When you pass work to someone who will look at thumbnails or ask a screen-reading tool for help:

1. Save a new version with the studio pattern before you share.

2. Open the shared folder (or attach the file) so the name is visible next to the preview.

3. In your note, quote the file name, not only “see screenshot.”

4. Name the next owner.

One example of the difference a label makes on screen:

Weekly routine

About 15 minutes per active project, run by the project owner:

• Open 05_Review/ and 04_Out/ in a normal file-browser window. Scan for names that are cut off, vague or off-pattern.

• Rename download leftovers such as export (1) and copy before the next review call.

• Check that chat-bound or web-bound files still match the names on disk.

• Note any field-order changes that would hide the project code in a narrow column, and send them to the naming lead.

Checklists

Before a screen share or review call

• Review folder uses the studio naming pattern

• Versions are padded and current

• You can read the client or project code without widening the window

Before dropping files into a chat or onto a web page

• File already renamed on disk

• Attachment name matches the disk name

• Note quotes the file name

Weekly

• Review and Out folders scanned for vague names

• Screenshot-only nicknames removed or renamed on disk

• Questions sent to the naming lead

Check your names

Prisma: file-naming and folder-structure tools for creative studios. Paste a few of your current names or folder paths into Prisma Scanner. It’s free, needs no signup, and gives a score plus recommendations on where names break good practice. When you’re ready to fix them, Prisma Hub, the Prisma app for Mac, suggests names based on your own rules. It’s designed to fit into creative pipelines.

Open Prisma Scanner