Are handles, hashtags, mentions and emoji preserved exactly?

Yes. The @handle is kept with its server or domain, hashtags keep their hash, links are returned as the text shown rather than the underlying address, and emoji are kept as characters rather than described. Where a display name and a handle differ, both are reported.

Can it work out who said what in a chat screenshot?

Bubble alignment, colour, avatars and any name labels are used to attribute each message, and the order is read from the top of the capture down. Where a conversation is genuinely ambiguous — two participants, no names, both bubbles the same colour — the attribution is reported as uncertain rather than invented.

What happens to text that ends in an ellipsis?

It is transcribed as far as it is visible and marked as truncated. Nothing is completed from context, because the missing words are not in the image. The same applies to a row cut off by the bottom edge of the capture or a chip sliced by the side of the screen.

Will menu and button labels end up mixed into my text?

Only if you want them. Interface elements are identified as such and can be returned in a separate list, omitted, or kept in place with a label. For documentation work the interface strings are the point; for archiving a post they are noise.

Can it read a photograph of a screen rather than a screenshot?

Often, but expect the small type to suffer. Screen photographs bring moiré from the pixel grid, reflections, and a perspective that makes one side of the display smaller than the other. If the figures in a status bar or a timestamp matter, retake it with the device’s screenshot function.

English

Tell the interface apart from what people wrote

Most of the words in a screenshot were put there by the software, not by a person: menus, tab labels, a battery percentage, a button that says Configure. The part you actually want is usually a few lines in the middle, half of it ending in an ellipsis because the window was too narrow. Evidano separates the content from the chrome, keeps the handle, timestamp and counts attached to the message they belong to, and says plainly where the text was cut off.

Upload a page

Sample pages

The centre column of a dark-mode Mastodon web timeline, showing posts with display names, handles, relative timestamps and action counts — Sample 1. The home timeline of a Mastodon 4.3.1 web client in its dark theme, from a screenshot whose posts and names were replaced by the uploader. Each entry carries a display name, an @handle that usually includes the server, a relative timestamp such as “5h”, a row of action icons with counts, and above some of them a line reading “Eugenio boosted” or “Replied to Antonio” that belongs to the post beneath it. One post has an attached image labelled with ALT and Hide badges.

A webmail inbox screenshot with a folder sidebar showing unread counts and a message list of demonstration conversations — Sample 2. The folder tree and conversation list of the Zimbra Collaboration webmail client, published by the vendor with demonstration accounts and messages. Folders carry unread counts in brackets, each conversation shows the participants, a subject, the first words of the message cut off at the edge of the column, a date and a flag, and threaded conversations are marked with an expand arrow and the number of messages in a circle.

A LibreOffice Calc window showing a blood pressure tracking sheet with coloured cells, three charts and a status bar — Sample 3. LibreOffice Calc 6.4 on Ubuntu, with a blood pressure tracking template open. Three separate populations of text share the window: the application’s menus, toolbars, name box and status bar; the sheet itself, with column headings, dated rows and a red-bordered warning note; and the axis labels and legends inside three embedded charts. The sheet tabs at the foot show that this is one of two sheets.

Date	Time	Systolic	Diastolic	Heart Rate	Weight	Pulse Pressure	MAP
10/14/2018	10:25	120	85	85	200.0	35	96.7
10/15/2018	10:25	121	82	88	198.0	39	95.0
10/16/2018	10:25	124	84	86	196.0	40	97.3

A mobile email app screenshot with a status bar, filter chips along the top, a promotional notification card and an empty message list — Sample 4. The inbox screen of a mobile email application, captured on an Android handset. The status bar reports the time, the network and a battery figure; a row of filter chips runs across the top with the last one sliced by the edge of the screen; a promotional card offers to configure notifications; and below it the list is empty. Almost every word on this capture was written by the application rather than by a person.

What is actually on the screen

A screenshot has layers in the same way a scanned page does, but they are stacked rather than spread out. At the outside is the operating system: a clock, a signal indicator, a battery figure, a home bar. Inside that is the application: a title bar, menus, toolbars with tooltips, a sidebar of folders with unread counts in brackets, tabs at the bottom of a spreadsheet, a status bar reporting the sheet number and the zoom level. Inside that again is the document or the feed. Floating over everything there may be a dialog, a notification, a cookie banner or a tooltip that hides part of what is underneath.

Feeds and conversations carry their own grammar. A display name and an @handle are different strings and both matter. A post may be prefixed with a line saying who boosted or shared it, or who it replies to, which belongs to the post below rather than the post above. Timestamps are relative — “5h”, “yesterday” — and the absolute time only appears on hover. Reaction, reply and share counts sit under the message as bare numbers; hashtags, mentions and links are styled differently from ordinary words; an attached image may carry its own badges, such as ALT or Hide. In a chat, the sender is encoded in which side of the screen the bubble sits on and nowhere else.

The screen also does things to text that paper never does. A long subject line is truncated with an ellipsis; a filter chip is sliced in half at the edge of the display; a cell’s contents are clipped by the next cell rather than wrapped; a list continues past the bottom of the capture, so the screenshot is a window on something larger. Dark themes invert the contrast, and a screenshot that has been shared through two messaging apps arrives re-compressed, with the small type softened into grey.

Why ordinary OCR struggles here

Chrome reads exactly like content

“File”, “Edit”, “Home”, “Explore”, “Profile” and “Delete” are perfectly ordinary English words, and a text extractor has no reason to treat them differently from a sentence someone typed. Dumped into one stream they surround the real message with menu labels, and on a screenshot of an empty inbox they are all you get.

Panes, columns and conversation order

A mail client shows a folder tree, a message list and a reading pane at once; a social client shows a composer, a timeline and a trending sidebar. Read line by line these interleave. Working out which pane is the content, and then which order the messages in it run, is a question about the interface rather than about the pixels.

Text that was never fully shown

An ellipsis at the end of a preview means the sentence continues somewhere the screenshot cannot reach. Completing it is a fabrication, and dropping the ellipsis hides the fact that the text is partial. The same applies to a row clipped by the bottom of the window and a label sliced by the edge of the screen.

Interface type is small and often re-compressed

Status bars and metadata are set at ten or eleven pixels, which is legible on the original display and marginal once the image has been scaled down and passed through two rounds of JPEG. The characters that suffer first — digits in a timestamp, a count, a version number — are the ones people screenshot the interface to record.

Who works with this material

Support and quality assurance teams

Bug reports arrive as screenshots of error dialogs, console output and half-loaded pages. Getting the exact wording of a message, the version number in the status bar and the identifier in a stack trace into text is what makes a ticket searchable and lets a duplicate be found before someone investigates it twice.

Researchers and journalists archiving posts

A post can be edited or deleted, and a screenshot is often the only record. Capturing the handle, the display name, the timestamp and the counts as separate fields, rather than as a run of text, is what makes a set of captures analysable and citable later.

Technical writers and accessibility reviewers

Documentation and audits depend on quoting interface labels exactly as they appear, including capitalisation and the wording of tooltips. Pulling the strings out of a set of captures is faster than retyping them and much less likely to introduce a label that does not exist in the product.

Compliance and evidence handling

Screenshots of messages and transactions are routinely submitted as evidence. What is needed is a faithful reading, an explicit note where an overlay hides text or a line is truncated, and no reconstruction of the parts the capture does not show.

Getting the best transcription

Step 1

Capture rather than photograph

Use the device’s own screenshot function at full resolution and send the original file. A photograph of a monitor adds moiré, glare and keystone distortion to type that was already small, and a screenshot that has been pasted into a document and re-exported has usually lost the metadata line you wanted to read.

Step 2

Say which part of the screen you care about

Name the region — the message list, the centre column, the dialog — or ask for interface chrome to be collected separately from content. On a capture of an empty screen that distinction is the whole result; on a busy one it removes several hundred words you would otherwise have to filter out.

Step 3

Ask for conversations as structured turns

For a chat or a feed, request each message as a record with author, handle, timestamp, text and counts, and say how boost or reply prefixes should be attached. That is far more useful than a paragraph, and it makes the order of the conversation explicit rather than implied by position.

Step 4

State the rule for truncation and overlays

Decide whether a preview ending in an ellipsis should be marked as incomplete, and whether text hidden behind a tooltip or a notification should be reported as obscured. Both are cases where the honest answer is a flag, and both are cases where a model left to itself may quietly finish the sentence.

Frequently asked questions

Are handles, hashtags, mentions and emoji preserved exactly?: Yes. The @handle is kept with its server or domain, hashtags keep their hash, links are returned as the text shown rather than the underlying address, and emoji are kept as characters rather than described. Where a display name and a handle differ, both are reported.
Can it work out who said what in a chat screenshot?: Bubble alignment, colour, avatars and any name labels are used to attribute each message, and the order is read from the top of the capture down. Where a conversation is genuinely ambiguous — two participants, no names, both bubbles the same colour — the attribution is reported as uncertain rather than invented.
What happens to text that ends in an ellipsis?: It is transcribed as far as it is visible and marked as truncated. Nothing is completed from context, because the missing words are not in the image. The same applies to a row cut off by the bottom edge of the capture or a chip sliced by the side of the screen.
Will menu and button labels end up mixed into my text?: Only if you want them. Interface elements are identified as such and can be returned in a separate list, omitted, or kept in place with a label. For documentation work the interface strings are the point; for archiving a post they are noise.
Can it read a photograph of a screen rather than a screenshot?: Often, but expect the small type to suffer. Screen photographs bring moiré from the pixel grid, reflections, and a perspective that makes one side of the display smaller than the other. If the figures in a status bar or a timestamp matter, retake it with the device’s screenshot function.

Related scripts and pages

Tables and Structured ContentGrids on screen and on paper, where a cell’s meaning comes from its row and column.Signs, Labels, and Printed MaterialsText designed to be looked at rather than read, where size and placement set the order.Handwritten ContentThe paper equivalent: notes, letters and registers where the layout carries the structure.All English hands and document typesEvery English domain, from Insular minuscule to timetables and app captures.Image to TextSearch all supported languages, scripts and document types.

Get the words out of a screenshot

Upload a capture of a chat, a feed, a spreadsheet or an error dialog, choose Screenshots and Digital Captures, and say which part of the screen you want.

Tell the interface apart from what people wrote

Sample pages

Evidano Transcription

Evidano Transcription

Evidano Transcription

Evidano Transcription

What is actually on the screen

Why ordinary OCR struggles here

Chrome reads exactly like content

Panes, columns and conversation order

Text that was never fully shown

Interface type is small and often re-compressed

Who works with this material

Support and quality assurance teams

Researchers and journalists archiving posts

Technical writers and accessibility reviewers

Compliance and evidence handling

Getting the best transcription

Capture rather than photograph

Say which part of the screen you care about

Ask for conversations as structured turns

State the rule for truncation and overlays

Frequently asked questions

Related scripts and pages

Get the words out of a screenshot

Company

About

Preview Evidano

Account

Newsletter