Vision AI in Google Cloud: Teaching Computers to See and Understand Images and Video

Vision AI in Google Cloud: Teaching Computers to See and Understand Images and Video

A complete, plain-English guide to Google Cloud's vision capabilities: ready-made image analysis, document reading, video understanding, custom-trained models and multimodal AI, with advice on choosing, securing, scaling and paying for each.

Think about how effortlessly you glance at a photograph. In a fraction of a second you know it shows a dog on a beach at sunset, that a sign in the background says “No Swimming,” and that a child is laughing. Now imagine you had to do that for ten million photographs, every day, without getting tired or bored, and then write down the results in a spreadsheet. No team of humans could keep up. Vision AI is the set of services that gives your applications a pair of tireless eyes and a trained brain behind them. You show them a picture, a scanned form or a video stream, and they tell you what is in it, what it says, what is happening and whether anything looks wrong.

This guide starts from zero. You do not need to know machine learning, mathematics or programming. Every new word is explained with what it is, why it exists, where it is used, an everyday comparison and a practical example. By the end you will understand the family of Google Cloud vision services, know which one fits which job, understand how images flow through them, and know how to keep the results accurate, secure, responsible and affordable.

1What Is Vision AI?

Vision AI is the umbrella for Google Cloud services that let software analyse images, documents and video.

The Short Definition

Computer vision is the field of teaching machines to extract meaning from pictures. A picture to a computer is nothing but a grid of numbers describing colours. Computer vision uses trained models to turn that grid into useful statements such as “this is a bicycle,” “this line reads Total: 42.50,” or “this product has a scratch.” Google Cloud offers this ability in several forms so that you can pick the amount of effort and control you need: ready-made services that work immediately, tools to train your own model on your own pictures, and general multimodal models that can look at an image and answer questions about it in everyday language.

Why It Exists

Organisations hold enormous piles of visual information: product photos, scanned invoices, security footage, medical images, satellite pictures, user-uploaded content. Most of it was invisible to software, so people had to look at it and type the facts into a system. Vision AI exists so that the facts can be pulled out automatically, making visual data searchable, measurable and actionable.

Where It Is Used

Typical uses include reading text from photographs and scans, tagging and organising photo libraries, moderating user-uploaded images, searching a catalogue by taking a picture, inspecting products on a factory line, counting people or vehicles in video, extracting data from invoices and forms, and describing images for accessibility.

Simple Analogy

A team of expert assistants sitting at the end of your mail room. One reads every handwritten label, another recognises the objects in every package photo, another flags anything inappropriate, and another watches the conveyor belt for damaged goods. You can hire ready-trained assistants, train your own for special jobs, or hire a versatile generalist who answers any question about any picture.

Ready-made
pretrained services you call immediately
Customisable
train models on your own labelled images
Multimodal
general models that reason over images and text together
i
Good to Know

“Vision AI” is a family, not one product. Names and groupings of products change over time, so this guide focuses on the capabilities and when to use each, and reminds you to confirm current product names in Google’s documentation.

2How Computers See: The Basics

A little background makes every later chapter easier.

Pictures Are Numbers

A digital image is a grid of tiny dots called pixels. Each pixel has numbers describing its colour. A photo of a few million pixels is a few million numbers. Early programs tried to recognise objects with hand-written rules, such as “a face has two circles above a line,” and failed whenever lighting, angle or style changed.

Learning from Examples

Modern vision uses machine learning, in which a model is shown millions of example images with correct labels and gradually adjusts itself until it can label new images correctly. The model that results does not store the pictures. It stores patterns, such as edges, textures and shapes, and how they combine into objects. The most common type is a neural network, a layered mathematical structure loosely inspired by the brain.

The Main Tasks

Task 1

Classification

Decide what the whole image is: cat, invoice, damaged part, normal part.

Task 2

Object Detection

Find objects and draw a box around each, saying what it is and where.

Task 3

Segmentation

Outline the exact shape of each object, pixel by pixel.

Task 4

Text Recognition (OCR)

Read the words in an image and return them as text with positions.

Task 5

Tracking in Video

Follow objects or people from frame to frame and count or time them.

Task 6

Image Understanding and Description

Describe the scene, answer questions about it and reason about relationships.

Simple Analogy

Teaching a child to recognise animals by showing thousands of picture books. The child never memorises each page. Instead they pick up what makes a cat catlike: whiskers, ears, posture. Later, a cat they have never seen is still recognised.

!
Common Misconception

“The AI understands pictures the way humans do.” It recognises statistical patterns learned from examples. It can be impressively accurate and also confidently wrong, especially on unusual images unlike its training. Always measure accuracy on your own data.

3The Vision Family on Google Cloud

Here is a map of the main services, with one-line descriptions, so you always know where you are.

Service or capabilityWhat it doesEffort to start
Cloud Vision APIPretrained analysis of images: labels, text, faces, landmarks, logos, objects, safe-search and moreVery low: send an image, get answers
Vision API Product SearchMatch a photo against your own catalogue of product imagesMedium: build and maintain a catalogue
Document AIUnderstand documents: extract fields from invoices, forms, receipts, identity documents and custom layoutsLow to medium
Video Intelligence APIPretrained analysis of stored video: labels, shots, objects, text, people, explicit contentLow
Vertex AI image models (custom and AutoML)Train classification or detection models on your own labelled imagesMedium: need labelled data
Vertex AI Vision (streaming and warehouse)Build and run video analytics applications on camera streams, and store and search videoMedium to high
Visual inspection solutionsDetect defects in manufactured goods with specialised toolingMedium
Gemini and other multimodal modelsAnswer questions about images and video in natural language, extract information, describe and reasonLow: write a prompt
Image generation and editing modelsCreate or modify images from descriptionsLow (a different direction: making pictures, not reading them)
Simple Analogy

A tool shop. Some tools are ready to use straight from the shelf (Vision API). Some are specialist machines for a trade (Document AI, Video Intelligence). Some you build to your own pattern (custom models). Some are a versatile multi-tool that handles a surprising range of jobs (multimodal models). Picking the right tool saves time and money.

flowchart TD
  Q["What do you need to do with visual data?"] --> A["Common tasks on photos"]
  Q --> B["Understand documents and forms"]
  Q --> C["Analyse stored or live video"]
  Q --> D["Detect your own special categories"]
  Q --> E["Ask free-form questions about images"]
  A --> A1["Cloud Vision API"]
  B --> B1["Document AI"]
  C --> C1["Video Intelligence or Vertex AI Vision"]
  D --> D1["Custom training on Vertex AI"]
  E --> E1["Multimodal Gemini models"]
        
FIG 1 — Choosing a starting point by the question you are asking
i
Practical Note

Product lines are reorganised from time to time, with some names retired or merged. Check the current documentation for status before building on any specific service, especially newer or preview ones.

4Cloud Vision API: Ready-Made Image Analysis

The Cloud Vision API is the quickest way to get useful answers from a picture.

The Idea

You send an image, either as the picture’s data or as a pointer to a file in Cloud Storage, and you tell the service which kinds of analysis you want. It sends back structured results. There is no training, no model to host and no servers to manage. Because it is a pretrained, general-purpose service, it works well on common content and less well on very specialised content.

The Features

Feature 1

Label Detection

Names things in the picture, such as dog, beach, sunset, vehicle, with a confidence score for each.

Feature 2

Text Detection

Reads text in photographs, such as street signs, product packaging and screenshots.

Feature 3

Document Text Detection

Optimised for dense text such as pages and handwriting, returning pages, blocks, paragraphs and words with positions.

Feature 4

Object Localisation

Finds multiple objects and returns a box around each.

Feature 5

Face Detection

Finds faces and reports where they are, plus attributes like head angle and likelihood of emotions. It detects faces; it does not identify who they are.

Feature 6

Landmark and Logo Detection

Recognises well-known places and brand logos.

Feature 7

Safe Search Detection

Rates the likelihood that an image contains adult, violent, racy or other sensitive content, useful for moderation.

Feature 8

Image Properties

Reports dominant colours, handy for design tools and search by colour.

Feature 9

Web Detection

Finds where else an image or similar images appear on the web and related topics.

Feature 10

Crop Hints

Suggests good crops of an image for a given shape, such as a square thumbnail.

Simple Analogy

A photo-lab counter with a menu. You hand over a photo and tick the services you want: describe it, read the text, find the faces, check for anything unsuitable. The counter returns a filled-in form for each tick, without you needing to know how the lab works.

flowchart LR
  IMG["Image from app or Cloud Storage"] --> API["Cloud Vision API"]
  API --> L["Labels with confidence"]
  API --> T["Text with positions"]
  API --> O["Objects with boxes"]
  API --> S["Safe-search ratings"]
  API --> F["Faces and attributes"]
  L --> APP["Your application logic"]
  T --> APP
  O --> APP
  S --> APP
  F --> APP
        
FIG 2 — One image, several kinds of answers
!
Common Mistake

Requesting every feature for every image. Each feature requested is charged separately, so ask only for what you will use.

5Understanding Results: Confidence, Boxes and Positions

The service returns more than a verdict. Learning to read the details is what turns output into trustworthy decisions.

Confidence Scores

Many results include a score from zero to one showing how sure the model is. A label of “dog” at 0.98 is very likely right. A label of “bicycle” at 0.55 is a coin flip. Your application should choose a threshold below which it ignores or flags results. The right threshold depends on the cost of mistakes. Moderation may lower the threshold to catch more, while an automated approval may raise it to avoid errors.

Boxes and Coordinates

Object results come with a bounding box. Many services return positions as fractions of the image width and height, so they stay valid whatever the image size. Text results return the position of every word, which lets you highlight text on the picture or rebuild the layout.

Likelihood Levels

Some features, such as safe search and face emotions, return descriptive levels like very unlikely, unlikely, possible, likely and very likely rather than numbers. Pick which levels trigger action in your application.

Result typeWhat you receiveHow to use it safely
LabelsNames and scoresUse a threshold, and combine with other signals
TextWords, lines, positions, languageValidate formats, such as dates and totals, after reading
ObjectsNames, scores, boxesCheck box size and score, and handle overlapping boxes
Safe searchLikelihood levels per categoryRoute borderline cases to human review
FacesBoxes, angles, likelihoodsTreat as detection only; consider privacy and fairness
Simple Analogy

A weather forecast. “Ninety percent chance of rain” gets you carrying an umbrella, “fifty percent” makes you think twice. Nobody blames the forecast for a fifty-fifty call, but they would blame themselves for ignoring the numbers entirely.

i
Design Tip

Create three zones: clearly yes, clearly no, and unsure. Automate the first two and send the unsure zone to a person. This captures most of the savings while limiting risk.

6Reading Text: OCR in Depth

Optical character recognition turns pictures of words into real text. It is among the most valuable vision capabilities.

Two Kinds of Reading

Text in Scenes

  • Street signs, shop fronts, labels, number plates
  • Scattered words at odd angles and lighting
  • Best served by the general text detection feature
  • Output is a set of words and fragments with positions

Text in Documents

  • Scanned pages, forms, books, receipts
  • Dense text in neat blocks and columns, sometimes handwriting
  • Best served by document text detection or Document AI
  • Output preserves structure: pages, blocks, paragraphs, lines

Factors That Affect Accuracy

Image Quality

Sharp, well-lit, high-resolution images read much better. Blur, glare, shadows and low resolution cause errors.

Orientation and Skew

Tilted or rotated pages are harder. Straighten them when you can.

Language and Script

Many languages and scripts are supported, but accuracy varies. Providing a language hint can help in some cases.

Handwriting

Supported, but less accurate than printed text and more dependent on neatness.

Complex Layouts

Tables, multiple columns and stamped overlays can confuse reading order. Document-focused services handle these better.

Simple Analogy

A proofreader reading a book versus a passer-by reading roadside signs. The proofreader sits under a good lamp with clean pages. The passer-by glimpses words at speed from a moving car. Both can read, but expectations should differ.

Always Validate

After reading text, check that it makes sense. A total should equal the sum of the lines, a date should be a real date, and a postal code should have the right length. Validation catches the occasional misread digit before it becomes a costly error.

!
Common Mistake

Trusting OCR output blindly for money or identity data. A confused eight and three can change an amount. Validate with rules and have a human check anything that fails or is unusual.

7Document AI: Understanding Forms and Paperwork

Reading words is one thing. Knowing that a number is the invoice total is another. Document AI adds that understanding.

What It Adds

Document AI goes beyond OCR. It uses models trained for particular document types to identify named fields and structure: supplier name, invoice date, line items, tax, total. The result is a tidy set of fields rather than a long block of text. It also handles tables, checkboxes and signatures in supported processors.

Kinds of Processors

Type 1

General OCR and Layout

Extracts text and structure from any document.

Type 2

Specialised Processors

Pretrained for invoices, receipts, expense reports, bank statements, identity documents and similar types.

Type 3

Form Parsing

Finds key-value pairs and tables in general forms.

Type 4

Custom Processors

Trained or configured with your own labelled examples to extract fields unique to your documents.

Type 5

Classification and Splitting

Decide what type of document it is, and split a combined scan into separate documents.

Type 6

Generative Extraction Options

Newer options use large models to extract fields with little or no labelled training data. Check current availability.

A Typical Document Pipeline

1

Documents arrive

Scans, photos or PDFs land in Cloud Storage or arrive by email.

2

Classify and split

Decide what each document is and separate merged scans.

3

Extract fields

The matching processor returns structured fields with confidence scores.

4

Validate and review

Rules check totals and dates. Low-confidence documents go to a human reviewer.

5

Store and use

Clean data lands in BigQuery or a business system, ready for payment, reporting or search.

flowchart TD
  IN["Scanned documents in Cloud Storage"] --> CL["Classify and split"]
  CL --> EX["Specialised or custom processor extracts fields"]
  EX --> VAL["Validation rules"]
  VAL -->|"high confidence"| OK["Write to BigQuery or business system"]
  VAL -->|"low confidence"| HR["Human review queue"]
  HR --> OK
  OK --> USE["Payments, reports, search"]
        
FIG 3 — A document processing flow with human review for doubtful cases
Simple Analogy

A mail clerk who knows what an invoice looks like. Plain OCR is a person who can read any language but has no idea what matters. Document AI is the clerk who immediately finds the date, the amount due and the supplier, and writes them into the right boxes on your system.

i
Practical Tip

Start with a specialised pretrained processor if one matches your documents. Move to a custom one only when pretrained fields do not cover your needs, since custom work needs labelled examples and upkeep.

8Product Search: Find Items by Photo

Visual search lets a customer photograph something and find matching products in your catalogue.

How It Works

You maintain a catalogue of products with one or more reference images each, organised into product sets and given categories such as apparel or homegoods. The service builds a searchable index of the visual features of those images. When a customer submits a query photo, the service finds the catalogue items that look most similar and returns them ranked with scores. Updates to the catalogue take some time to be reflected in the index.

What Makes It Work Well

Good Reference Images

Clear photos from several angles, on plain backgrounds, with consistent quality.

Accurate Categories

Assign each product to the right category so the matching engine knows what to compare.

Bounding Region Hints

When a customer’s photo contains many items, narrowing to the region of interest improves results.

Catalogue Hygiene

Remove discontinued items and fix mislabelled ones so results stay relevant.

Simple Analogy

A shop assistant with a photographic memory of every item on the shelves. A customer holds up a picture from a magazine, and the assistant instantly says, “We have three things very close to that, here are the best matches.”

!
Common Mistake

Using low-quality or inconsistent reference photos. The search can only be as good as the catalogue images. Invest in a clean, standard photo process.

i
Practical Note

Newer image and multimodal embedding approaches combined with vector search can also power visual search. Compare the dedicated product search service with those options for your catalogue size and needs.

9Video Intelligence API: Understanding Stored Video

Video is images in sequence with sound. Video analysis finds structure and events inside that sequence.

What It Can Tell You

Feature 1

Label Detection

What appears in the video overall, in segments, and in individual shots.

Feature 2

Shot Change Detection

Finds the moments where the camera cuts to a new scene, helping to index and summarise.

Feature 3

Object Tracking

Follows detected objects across frames with boxes over time.

Feature 4

Text Detection in Video

Reads on-screen text such as captions, signs and scoreboards, with time stamps.

Feature 5

Explicit Content Detection

Flags frames likely to contain adult content, for moderation.

Feature 6

Speech Transcription

Converts spoken audio into text with time stamps.

Feature 7

Person and Face Detection

Detects people and faces appearing in video, again for detection and not identification.

How a Job Runs

Video files are large, so analysis normally runs as a background job. You point the service at a video in Cloud Storage and choose features. It returns a job reference and later delivers the results, which you collect and store. Results include time offsets so you can jump to the exact moment something happens.

sequenceDiagram
  participant A as Your application
  participant S as Cloud Storage
  participant V as Video Intelligence
  A->>S: Upload video file
  A->>V: Request analysis with chosen features
  V-->>A: Return job reference
  V->>S: Read video
  V->>V: Analyse frames and audio
  A->>V: Check job status
  V-->>A: Results with time offsets
  A->>A: Store results in BigQuery or search index
        
FIG 4 — Asynchronous analysis of a stored video
Simple Analogy

A film archivist who watches your reels overnight and leaves an index card for each: the scenes, the people, the signs on screen and a transcript. Next morning you can jump straight to “the scene with the red car.”

i
Cost Tip

Video is billed by the minutes analysed, per feature. Analyse only the features you need, and consider processing shorter clips or lower-priority footage selectively.

10Live Video Analytics: Vertex AI Vision

When cameras produce video continuously, you need an always-on pipeline rather than one-off jobs.

The Concept

Vertex AI Vision is a platform for building applications that process video streams, from ingest to analysis to storage and alerts. You connect camera or video streams, drag processing steps onto an application canvas, and send the results to destinations such as BigQuery or a video warehouse. Typical steps include occupancy counting, person and vehicle detection, personal protective equipment detection, and custom models you have trained yourself.

The Main Parts

Streams

Named live video sources that cameras or encoders send into the platform.

Applications

Visual flow diagrams combining inputs, processing models and outputs.

Pretrained and Custom Models

Ready-made analytics for common needs, and the option to plug in your own trained models.

Warehouse

A place to store large volumes of video and search it by content and metadata.

Outputs

Detected events and statistics sent to BigQuery, Pub/Sub or other systems for dashboards and alerts.

flowchart LR
  CAM["Cameras and encoders"] --> ST["Video streams"]
  ST --> APP["Analytics application"]
  APP --> M1["Person and vehicle detection"]
  APP --> M2["Occupancy counting"]
  APP --> M3["Custom model"]
  M1 --> OUT["BigQuery statistics"]
  M2 --> OUT
  M3 --> ALR["Pub/Sub alerts"]
  ST --> WH["Video warehouse for search"]
  OUT --> DASH["Dashboards"]
        
FIG 5 — A live video analytics application

Design Concerns

1

Bandwidth and encoding

Many cameras at high resolution need large, steady network capacity. Choose resolution and frame rate to match the task.

2

Latency expectations

Cloud analysis adds delay. For split-second safety decisions, processing near the camera may be needed.

3

Privacy and retention

Decide what is recorded, how long it is kept, who can watch it, and whether people are anonymised.

4

Continuous cost

Streams and running applications bill continuously, so remove unused ones.

Simple Analogy

A security control room with a wall of screens and a team of watchers who never blink. Each watcher has one job: count people, spot helmets, notice a blocked doorway. When something matters they ring a bell and write a log entry.

!
Common Mistake

Streaming full-resolution video from every camera “just in case.” Bandwidth and processing cost rise sharply. Match resolution, frame rate and number of analysed cameras to the real question being asked.

i
Practical Note

This product area has evolved quickly, with features and packaging changing. Confirm the current status, supported models and regions in the documentation before planning a large deployment.

11Custom Models: Training Your Own Vision AI

When the ready-made services do not know your special categories, you teach a model with your own pictures.

When You Need One

Pretrained services recognise common things. They cannot tell the difference between two nearly identical machine parts, spot a specific defect in your product, or classify skin conditions, crop diseases or specialised equipment unless they have been trained on such examples. A custom model learns your categories from your labelled images.

The Training Journey

1

Define the task

Classification (what is it), detection (where is it) or segmentation (exact outline). Decide the categories and what “good enough” accuracy means.

2

Collect images

Gather pictures that represent real conditions: lighting, angles, backgrounds, cameras, seasons and the full range of categories including rare ones.

3

Label the images

Add the correct answers: category tags or boxes. Quality here matters more than almost anything else. Clear guidelines and a review step reduce mistakes.

4

Split into train, validation and test sets

Most images teach the model, some tune it, and a held-back set measures honest performance.

5

Train

Use automated training, which chooses and tunes a model for you, or custom training where your team controls the model design.

6

Evaluate

Look at accuracy measures and at the specific mistakes, especially for rare and costly categories.

7

Deploy and monitor

Make the model available to applications, and watch for performance drifting as the real world changes.

Automated versus Custom Training

ApproachYou provideStrengthTrade-off
Automated training (AutoML-style)Labelled imagesNo machine learning expertise needed; strong baselinesLess control; cost grows with training hours
Custom trainingYour own training code and dataFull control of architecture and tuningNeeds ML engineers
Fine-tuning a large pretrained modelSmaller labelled setsNeeds less data, good accuracyRequires careful evaluation and some expertise
flowchart TD
  D["Collect images"] --> L["Label images"]
  L --> S["Split into train, validation, test"]
  S --> T["Train model"]
  T --> E["Evaluate on test set"]
  E -->|"good enough"| DEP["Deploy to endpoint"]
  E -->|"not yet"| IMP["Add data, fix labels, adjust"]
  IMP --> L
  DEP --> MON["Monitor accuracy in production"]
  MON -->|"drift found"| D
        
FIG 6 — The loop of building and improving a custom vision model
Simple Analogy

Training a new quality inspector. You show them hundreds of good and bad parts, correct their mistakes, test them on parts they have never seen, and only then let them work the line while a supervisor keeps an eye out for slipping standards.

!
Common Mistake

Training on tidy studio photos and deploying on messy factory-floor images. The model has never seen shadows, dust or odd angles. Train on images that look like the real deployment.

12Data Quality: Labels, Balance and Bias

A model is only as good as its examples. Most failures trace back to data, not algorithms.

Common Data Problems

Wrong or Inconsistent Labels

If different people label the same thing differently, the model gets confused. Write labelling guidelines with example pictures and review a sample of work.

Imbalanced Classes

If 99 percent of pictures show normal parts, a model that always says “normal” is 99 percent accurate and useless. Collect more rare examples and measure accuracy per category.

Leakage Between Sets

Near-duplicate images in both training and test sets make results look better than reality. Keep sets separate and de-duplicate.

Narrow Coverage

Images from one camera, one site or one season may not represent others. Include variety.

Unrepresentative or Biased Samples

If some groups of people, skin tones, environments or styles are underrepresented, the model works worse for them. Check performance across subgroups before release.

Improving Data Efficiently

Method 1

Review Mistakes First

Look at where the model fails. Often a few label fixes or a few missing situations bring large gains.

Method 2

Augmentation

Create extra training variety by flipping, rotating, brightening or cropping existing images when appropriate.

Method 3

Active Learning

Prioritise labelling the images the model is least sure about, which teaches it the most.

Method 4

Human-in-the-Loop

Send uncertain predictions to reviewers and feed their corrections back as new training data.

Simple Analogy

Teaching with a textbook. If the textbook has errors, only shows one kind of example, or leaves out whole chapters, the student will learn wrongly and fail exams in the real world, however clever the student is.

i
Good Habit

Spend more of the project budget on data and evaluation than on tuning the model. In practice, better data beats cleverer algorithms.

13Multimodal Models: Asking Questions About Images

Large multimodal models, such as Google’s Gemini family, can look at images and video and respond in natural language.

What Changes

Older vision services answered fixed questions: labels, text, boxes. A multimodal model accepts an image together with a written instruction and responds flexibly. You can ask, “Describe this scene for a visually impaired user,” “List the items on this shelf and their prices,” “Does this photo show a damaged package? Explain,” or “Extract the fields from this form as a table.” No training is required for many tasks, because the model has broad general knowledge.

What They Are Good At

Strength 1

Description and Captioning

Natural descriptions, alt text for accessibility and summaries of scenes.

Strength 2

Question Answering

Answer specific questions about a picture, a chart, a diagram or a screenshot.

Strength 3

Flexible Extraction

Pull out information in a format you request, from messy or unusual documents.

Strength 4

Reasoning Across Images

Compare two photos, follow a sequence, or combine text and visuals.

Strength 5

Video Understanding

Summarise and answer questions about video clips, depending on model support.

Strength 6

Rapid Prototyping

Test an idea in an afternoon with a prompt before investing in a trained model.

What To Watch For

Benefits

  • No training data needed for many tasks
  • One model for many different questions
  • Handles unusual layouts and mixed content
  • Explanations in everyday language

Cautions

  • Answers can be fluent but wrong, known as hallucination
  • Outputs may vary between calls
  • Cost per image can exceed specialised services at high volume
  • Exact counting and precise measurements may be unreliable
  • Latency is usually higher than dedicated services
Simple Analogy

Hiring a clever, well-read generalist versus a specialist machine. The generalist can handle whatever you put in front of them, explains their thinking and adapts, but can sometimes be confidently mistaken and costs more per task than a purpose-built machine doing one job at scale.

!
Common Mistake

Using a multimodal model as the final authority for high-stakes decisions without verification. Combine it with rules, confidence checks, a second system or a human reviewer where errors are costly.

14Choosing the Right Approach

With so many options, a simple decision process saves time.

A Practical Ladder

1

Try a ready-made service first

If labels, text, objects or safe-search already answer your question, you are done in an afternoon.

2

Use a specialised service for documents or video

Document AI for paperwork, Video Intelligence or Vertex AI Vision for footage.

3

Prototype with a multimodal model

For flexible or unusual questions, test a prompt on a sample of real images.

4

Train a custom model

When you need high accuracy on your own categories at scale or low cost per image, or when generic models fail on your data.

5

Combine approaches

Use a cheap, fast model to screen, and a stronger or human review for uncertain cases.

SituationGood starting point
Tag photos and moderate uploadsCloud Vision API (labels, safe search)
Read street signs and packaging textVision API text detection
Process invoices and receiptsDocument AI specialised processors
Index and search a video libraryVideo Intelligence API, possibly with a warehouse
Count people in live camera feedsVertex AI Vision application with pretrained analytics
Find manufacturing defectsCustom model or visual inspection tooling
Describe images for accessibilityMultimodal model
Search a catalogue by photoProduct Search or embedding-based visual search
Unusual, one-off questions about imagesMultimodal model prompt
Simple Analogy

Getting a suit. Buy off the rack if it fits (ready-made), alter it if it nearly fits (specialised or fine-tuned), or commission a tailor for a perfect fit when it matters and you can afford the time (custom). Never commission a tailor for a T-shirt.

i
Practical Tip

Before committing, test each candidate on at least a few hundred of your real images and write down the accuracy and cost. Decisions based on measurements beat decisions based on demos.

15Architecture: How Image Data Flows

Whatever the model, the surrounding system follows a few common shapes.

Synchronous: Instant Answers

An application sends one image and waits for the answer, usually within a second or two. This suits interactive uses such as a mobile app that reads a label when the user takes a photo. Limits on image size and request rate apply.

Asynchronous: Batches and Large Jobs

For thousands of images, or for large files such as multi-page documents and videos, the application submits a batch job pointing to files in Cloud Storage, and results are written back to Cloud Storage when ready. This is more efficient, avoids tying up the caller, and handles failures per item.

Event-Driven: Process on Arrival

A new image landing in a Cloud Storage bucket generates an event. A small serverless function or workflow picks it up, calls the vision service, and writes results to a database or warehouse. This pattern scales automatically and requires no servers to manage.

flowchart TD
  U["User uploads image"] --> B["Cloud Storage bucket"]
  B --> EV["Storage event"]
  EV --> FN["Serverless function or workflow"]
  FN --> V["Vision service or model"]
  V --> FN
  FN --> DB["Results to BigQuery or database"]
  FN -->|"low confidence"| REV["Human review queue"]
  FN -->|"sensitive content"| QUA["Quarantine bucket"]
  DB --> APP["Search, dashboards, application features"]
        
FIG 7 — An event-driven image processing pipeline

Supporting Services

Part 1

Cloud Storage

Holds source images and output files, with lifecycle rules to control retention.

Part 2

Pub/Sub and Eventarc

Carry events and decouple upload from processing.

Part 3

Cloud Run and Functions

Run small pieces of glue logic without servers.

Part 4

BigQuery

Stores structured results for analysis, including joining with business data.

Part 5

Workflows and Composer

Orchestrate multi-step processing, retries and reviews.

Part 6

Vector Search

Find visually or semantically similar images using embeddings.

Simple Analogy

A photo processing factory with an intake desk, a conveyor belt, inspection stations and an output shelf. Photos enter at the desk, flow through the right stations, and the results are shelved in order. If a photo is unclear, it is diverted to a person.

!
Common Mistake

Processing thousands of images one synchronous call at a time from a single loop. It is slow, fragile and wasteful. Use batch jobs or event-driven parallel processing with retries.

16Image Preparation and Preprocessing

Small preparation steps before sending an image often improve accuracy and cut cost.

Useful Preparations

Resize Sensibly

Extremely large images add transfer time and cost without much benefit, while too-small images lose detail. Aim for the recommended range for the task, and keep text legible.

Correct Orientation

Phones store rotation as metadata. Make sure upright images are sent upright, especially for text.

Improve Contrast and Remove Noise

For scans, cleaning up shadows and speckles helps text reading.

Crop to the Area of Interest

Remove irrelevant borders so the model focuses on what matters.

Choose Good Formats

Use common formats and avoid heavy compression that blurs fine text or small details.

Remove Duplicates

Do not pay to analyse the same image repeatedly. Detect duplicates with simple fingerprints.

Simple Analogy

Handing a doctor a clear, correctly labelled X-ray rather than a crumpled photocopy held upside down. The doctor is equally skilled, but the better the input, the better the answer.

i
Practical Tip

Keep the original image and record which preprocessing was applied. That makes problems reproducible and lets you reprocess later with a better model.

17Security, Privacy and Access Control

Images often contain faces, documents and personal information. Treat them as sensitive data.

Controlling Access

Use Google Cloud identity and access management to give each application and person the minimum permissions needed. Services calling vision APIs should run under dedicated service accounts, scoped to only the buckets and APIs they require. Avoid long-lived downloadable keys, using attached identities instead. Keep input and output buckets separate, with different access.

Protecting the Data

Control 1

Encryption

Data is encrypted in transit and at rest by default. Customer-managed keys are available for stricter policies.

Control 2

Network Controls

Private connectivity and service perimeters can limit where data and API calls may travel.

Control 3

Data Location

Choose regional endpoints and storage locations that satisfy residency rules. Not every feature is available in every region.

Control 4

Retention and Deletion

Set lifecycle rules so images and results do not live longer than necessary.

Control 5

Redaction and Masking

Blur faces or remove sensitive text before storage or sharing, using sensitive data protection tools.

Control 6

Audit Logs

Record who accessed data and who called the services.

Understanding How Your Data Is Used

Read the data handling terms for each service: whether content is stored, for how long, and whether it may be used to improve models. Terms differ by service and may depend on your agreement, so confirm them before sending sensitive images, and document your findings for your compliance team.

flowchart TD
  IN["Input bucket: restricted write"] --> SVC["Processing service account: least privilege"]
  SVC --> RED["Redact faces and sensitive text if required"]
  RED --> VIS["Vision API or model in approved region"]
  VIS --> OUT["Output bucket and BigQuery: restricted read"]
  OUT --> RET["Retention and deletion rules"]
  AUD["Audit logs"] -.-> IN
  AUD -.-> VIS
  AUD -.-> OUT
        
FIG 8 — Layers of protection around image processing
Simple Analogy

A photo lab handling people’s private pictures. Staff wear badges for the areas they need, customers’ photos are kept in locked trays, scraps are shredded after the retention period, and a log records who handled which job.

!
Common Mistake

Leaving image buckets publicly readable “for convenience.” Photographs and scanned documents are among the most commonly exposed sensitive data. Keep buckets private and share through controlled, expiring links.

18Responsible AI: Fairness, Faces and Human Oversight

Vision systems affect real people. Building them responsibly protects users and your organisation.

Faces Deserve Special Care

Detecting that a face exists in a picture is different from identifying who it is. Identification and emotion inference raise serious privacy, consent and fairness concerns and are regulated in many places. Google’s detection features locate faces and describe visible attributes, but using any technology to identify people, track individuals or infer sensitive characteristics needs careful legal and ethical review, clear consent where required and strong safeguards.

Fairness

Vision models can perform differently for different groups, lighting conditions and environments. Test your system on diverse examples that reflect your real users. Measure error rates for subgroups, not just the average. If gaps appear, improve data, adjust thresholds or add human review.

Transparency and Human Oversight

Tell People

Be open about when images are analysed automatically, what is done with the results, and how people can object or appeal.

Keep a Person in the Loop

For decisions that significantly affect people, such as access, employment, eligibility or enforcement, make AI an assistant rather than the sole decider.

Provide a Way to Correct Mistakes

Make it easy to flag and fix wrong results, and learn from those corrections.

Assess Before You Launch

Carry out a risk review covering privacy, misuse, bias and failure impact, and document the decisions.

Simple Analogy

A security guard with a powerful pair of binoculars. The tool does not decide what is right. Good practice is clear rules about where it may be pointed, who may use it, how long observations are kept and how a mistaken suspicion is corrected.

i
Practical Note

Laws and platform policies about biometric and image analysis vary by country and are changing. Involve legal and privacy specialists early, and review Google’s acceptable use and responsible AI guidance for the services you use.

19Evaluating Accuracy and Quality

“It seems to work” is not a measurement. Good evaluation tells you when to trust the system.

Key Measures in Plain Words

MeasurePlain meaningWhy it matters
AccuracyShare of all answers that are rightMisleading when categories are imbalanced
PrecisionOf the things it flagged, how many were truly that thingLow precision means many false alarms
RecallOf all the real cases, how many it foundLow recall means missed problems
Confusion matrixA table of what was mistaken for whatShows exactly which categories get confused
Overlap measure for boxesHow well a predicted box matches the true boxNeeded for detection quality
Character or word error rateHow many characters or words were read wronglyStandard for text recognition

Precision versus Recall: A Trade-off

Raising the confidence threshold usually increases precision and lowers recall, and the reverse. A defect detector in a safety-critical product should favour recall, since missing a defect is worse than a false alarm. A moderation system on a small team might favour precision to avoid drowning reviewers.

Build a Golden Set

Collect a fixed set of images with trusted answers that represent the real mix, including hard cases. Re-run it whenever you change a model, a threshold or a prompt. This is the quickest guard against accidentally making things worse.

Simple Analogy

A smoke detector. If it is too sensitive, it screams at toast every morning and people stop listening. If it is not sensitive enough, it stays silent during a real fire. The right setting depends on what is at stake.

!
Common Mistake

Judging quality on a handful of impressive demo images. Demos are chosen to look good. Evaluate on a representative, randomly drawn sample, including ugly and ambiguous images.

20Operating in Production: Monitoring and Quotas

A model that worked at launch can quietly degrade. Operations keeps it healthy.

What To Monitor

Technical Health

Request volumes, error rates, response times and quota usage, through Cloud Monitoring and logging.

Result Quality

Distribution of confidence scores, share of results sent to human review, and spot-check accuracy on sampled production images.

Input Drift

Changes in the type of images arriving: new cameras, new lighting, new product designs, new languages. Drift quietly reduces accuracy.

Cost

Units processed per feature per day, tracked with budgets and alerts.

Quotas and Rate Limits

Each service limits requests per minute, image size, batch size and concurrent jobs. Learn the limits for the services you use, design clients that back off and retry politely when told to slow down, and request quota increases early for planned growth rather than during an incident.

Retraining and Updating

1

Collect feedback

Gather human corrections and misclassified examples from production.

2

Add to the training data

Label and include new situations, especially recurring failures.

3

Retrain and compare

Evaluate the new model on the golden set against the current one.

4

Roll out gradually

Send a small share of traffic to the new model, compare, then expand.

Simple Analogy

Maintaining a fleet of delivery vehicles. You watch fuel, breakdowns and delivery times, schedule regular servicing, and introduce a new model to a few routes before replacing the whole fleet.

i
Operations Tip

Store a sample of inputs with the model’s outputs and any human corrections. This archive becomes your best training data and your evidence when someone asks why a decision was made.

21Cost and Pricing

Vision AI is billed by usage. Knowing the units makes budgeting straightforward.

The Billing Units

ServiceTypically billed byCost drivers
Cloud Vision APINumber of images per feature requested, with a small monthly free allowance per feature and lower rates at higher volumesNumber of features per image, total volume
Document AIPages processed, with different rates per processor typePage counts, processor type, custom model hosting
Video Intelligence APIMinutes of video per featureLength of video, number of features
Vertex AI VisionStream and application running time, model usage and storageNumber of cameras, hours, models used, retention
Custom trainingCompute hours for training, plus hosting and prediction for deployed modelsTraining length, hardware, endpoint uptime
Multimodal modelsUnits of input and output, where images and video count as inputImage size, number of images, response length

Exact rates, free allowances, volume discounts and unit definitions change and vary by region, so always use the current pricing pages and the pricing calculator for estimates. What stays constant are the drivers: how many items you process, how many analyses you request on each, how long deployed resources run, and which service tier you choose.

Ways to Save

1

Request only the features you need

Each feature on each image is a billable unit.

2

Filter before analysing

Skip duplicates, blank frames and irrelevant files with cheap checks.

3

Sample video sensibly

Analyse key frames or shorter intervals instead of every frame when the task allows.

4

Cascade models

Use a cheap, fast model for the first pass and a costlier one only on uncertain cases.

5

Cache results

Store the answers for images you have already analysed.

6

Shut down idle endpoints and streams

Deployed models and running streams bill while they exist.

7

Use batch processing

Batch jobs are efficient and avoid per-request overheads for non-urgent work.

!
Common Mistake

Leaving a custom model endpoint or a camera stream running after an experiment. These bill by the hour, and forgotten resources can cost more than the actual analysis.

i
Cost Tip

Run a pilot on a few thousand real images, record cost per image, then multiply by expected volume with a safety margin. Set budget alerts before the pilot expands.

22Edge and Hybrid Scenarios

Sometimes the picture cannot or should not travel to the cloud.

Why Process Near the Camera

Reason 1

Latency

A robot arm or safety stop cannot wait for a round trip to a distant region.

Reason 2

Bandwidth

Hundreds of high-resolution cameras can overwhelm a site’s internet link.

Reason 3

Privacy and Residency

Some images must not leave a building or a country.

Reason 4

Connectivity

Remote sites may have unreliable networks and need to work offline.

Hybrid Pattern

A common design runs a compact model on a device or local server for instant decisions, sends only exceptions, summaries or sampled images to the cloud, and uses cloud resources to train better models and push updates back to the sites. Trained models can often be exported to lightweight formats suitable for devices. Check the export options of the service you use.

flowchart LR
  CAM["Camera on site"] --> EDGE["Local device runs compact model"]
  EDGE -->|"instant action"| LOCAL["Local alarm or machine control"]
  EDGE -->|"exceptions and samples"| CLOUD["Cloud Storage and BigQuery"]
  CLOUD --> TRAIN["Retrain and evaluate in the cloud"]
  TRAIN --> PUSH["Updated model package"]
  PUSH --> EDGE
        
FIG 9 — Edge decisions with cloud learning
Simple Analogy

A factory inspector standing at the line, making quick calls on the spot and phoning headquarters only about unusual cases. Headquarters studies those cases, improves the guidebook, and sends the new edition back to every inspector.

i
Practical Note

Edge deployment adds work: device management, secure updates and monitoring fleets. Choose it when latency, bandwidth or privacy truly require it.

23Advantages, Disadvantages and Trade-offs

Every approach has strengths and costs. Here is an honest balance sheet.

Advantages

  • Immediate results from ready-made services with no model building
  • Wide range of capabilities from images to documents to live video
  • Scales to millions of images without managing servers
  • Smooth path from quick prototype to custom model
  • Integrates with storage, analytics, orchestration and security services
  • Multimodal models add flexible, language-driven understanding

Disadvantages / Trade-offs

  • Pretrained models can fail on specialised or unusual images
  • Custom models need labelled data, expertise and ongoing care
  • Costs grow with volume and with the number of features requested
  • Results are probabilities, not certainties
  • Privacy, fairness and legal responsibilities are significant
  • Product names and packaging change, requiring ongoing attention
  • Multimodal outputs can be wrong yet convincing
“A vision model is a very fast, very tireless assistant, but it is still an assistant. Measure it, bound it and keep a person ready.”

The Decision in One Sentence

Start with the simplest ready-made service that answers your question, measure it on your own images, and add specialisation, custom training or multimodal reasoning only where the measurements show a real gap.

24Design Patterns That Work

A pattern is a proven shape for a solution. These recur in successful vision projects.

Pattern: Cascade from Cheap to Expensive

A fast, inexpensive check removes obvious cases, and a stronger model or person looks only at what remains.

Pattern: Three Zones of Confidence

Automate clear results, reject clear negatives and review the uncertain middle.

Pattern: Event-Driven Processing

Process each image when it arrives, writing results to a warehouse for analysis.

Pattern: Validate Extracted Data

Apply business rules to OCR and field extraction, catching impossible values before they enter systems.

Pattern: Golden Set for Every Change

Re-run a fixed evaluation set before changing any model, threshold or prompt.

Pattern: Feedback Loop

Human corrections flow back into labelled data and retraining on a schedule.

Pattern: Prototype with Prompts, Industrialise with Models

Prove value quickly with a multimodal model, then replace high-volume parts with cheaper specialised or custom models.

Pattern: Embeddings for Similarity

Convert images to numeric fingerprints and search by similarity for duplicates, recommendations and visual search.

flowchart TD
  IMG["Incoming images"] --> PRE["Preprocess and de-duplicate"]
  PRE --> FAST["Fast screening model"]
  FAST -->|"clearly fine"| DONE["Record result"]
  FAST -->|"uncertain or flagged"| STR["Stronger model or multimodal check"]
  STR -->|"confident"| DONE
  STR -->|"still unsure"| HUM["Human review"]
  HUM --> DONE
  HUM --> LBL["Corrections become new labelled data"]
  LBL --> RT["Scheduled retraining"]
  RT --> FAST
        
FIG 10 — A cascade with human review and a learning loop

25Anti-Patterns to Avoid

An anti-pattern looks like a good idea but quietly causes trouble. These are the most common.

ANTI-PATTERN-01 Avoid
Problem

Judging a solution on a few polished demo images.

Why It’s Harmful

Real images are messier. A system that dazzles in a demo can disappoint in production.

Correct Approach

Evaluate on a representative sample drawn at random from real data, including difficult cases.

ANTI-PATTERN-02 Avoid
Problem

Training a custom model when a ready-made service would already do the job.

Why It’s Harmful

Weeks of labelling and maintenance for no gain, plus ongoing operational burden.

Correct Approach

Try ready-made and multimodal options first, and train only when measurements show they fall short.

ANTI-PATTERN-03 Avoid
Problem

Requesting every available feature on every image.

Why It’s Harmful

Each feature is billed, so cost multiplies while most results go unused.

Correct Approach

Request only features that feed a decision, and cache results.

ANTI-PATTERN-04 Avoid
Problem

Treating model output as certain and automating high-stakes decisions entirely.

Why It’s Harmful

Errors reach customers or employees without any chance of correction, creating harm and liability.

Correct Approach

Use confidence thresholds, validation rules and human review for consequential decisions.

ANTI-PATTERN-05 Avoid
Problem

Training on clean images and deploying on messy real ones, or never retraining.

Why It’s Harmful

Accuracy collapses or slowly decays as the world changes, often unnoticed.

Correct Approach

Train on realistic data, monitor production quality and retrain on a schedule using feedback.

ANTI-PATTERN-06 Avoid
Problem

Public buckets of images and broad permissions for service accounts.

Why It’s Harmful

Personal images and documents leak, and one compromised account exposes everything.

Correct Approach

Keep buckets private, use least-privilege service accounts, set retention, and audit access.

ANTI-PATTERN-07 Avoid
Problem

Using face detection or emotion estimates to identify, rank or judge people without review.

Why It’s Harmful

It raises serious privacy, fairness and legal problems, and the signals are not reliable measures of identity or intent.

Correct Approach

Limit use to clearly lawful, consented purposes, test for fairness and keep human oversight.

ANTI-PATTERN-08 Avoid
Problem

Leaving endpoints, streams and test resources running.

Why It’s Harmful

They bill continuously, and forgotten experiments can cost more than production.

Correct Approach

Tag resources with owners and end dates, set budget alerts, and clean up after experiments.

26Best Practices and Common Mistakes

A checklist of habits shared by teams that ship vision projects successfully.

Do This

  • Define the business question and the cost of each type of error first
  • Start with ready-made services and measure on real images
  • Build a golden evaluation set and reuse it for every change
  • Use confidence thresholds with a human review zone
  • Validate extracted data with business rules
  • Prepare images sensibly and avoid duplicates
  • Keep data private, with least-privilege access and retention rules
  • Monitor quality, drift, quotas and cost in production
  • Document limitations and involve privacy and legal teams early

Avoid This

  • Launching without measuring accuracy on representative data
  • Over-engineering with custom models too soon
  • Ignoring rare but critical categories
  • Sending sensitive images without understanding data handling terms
  • Assuming one average accuracy number applies to every group
  • Forgetting to retrain as conditions change
  • Letting experiments run up unnoticed bills

Start Small, Then Grow

Pick one valuable, well-bounded use case, such as reading a single type of document or tagging one product line. Build the full path from image to decision, with evaluation, review, monitoring and cost tracking. Then extend to more cases. Teams that attempt everything at once often deliver nothing reliable.

Talk to the People Who Do the Job Today

The inspectors, clerks and moderators currently doing the work know the tricky cases. Involve them in labelling, in defining rules and in reviewing results. Their knowledge is often the difference between a model that impresses and one that is actually useful.

Plan for Change

Models, product names, limits and prices change. Keep your integration behind a thin layer in your own code so you can swap a service or model without rewriting everything, and keep your golden set so you can compare replacements quickly.

!
Common Mistake

Treating the launch as the finish line. A vision system is a living service. Data changes, cameras change and people find new ways to confuse it. Budget for ongoing monitoring and improvement.

27Real-World and Industry Scenarios

These are illustrative scenarios showing how organisations typically use vision services, not claims about specific companies.

Retail and E-commerce: Visual Search and Catalogue Quality

Shoppers photograph an item to find similar products. Behind the scenes, image checks flag poor-quality supplier photos, and labels help organise millions of listings.

Banking and Insurance: Paperwork Automation

Applications, claims and identity documents are scanned, classified and read. Fields are validated, and unusual cases go to a specialist, cutting processing time.

Manufacturing: Visual Inspection

Cameras on the line photograph each part. A custom model flags scratches, missing components or misalignment, with rejected parts routed for human inspection.

Media and Social Platforms: Content Moderation

Uploads are screened for unsafe content using safe-search ratings, with borderline items queued for human moderators.

Healthcare and Life Sciences: Image Triage Support

Specialist models help prioritise scans or slides for expert review. Strict governance, validation and human oversight apply because of the stakes.

Agriculture and Environment: Field and Satellite Images

Custom models classify crop health, detect pests, or track land use from aerial and satellite imagery.

Logistics and Transport: Reading Labels and Counting

Text recognition reads shipping labels and vehicle markings, while video analytics counts vehicles and monitors yard occupancy.

Public Spaces and Buildings: Occupancy and Safety

Anonymous counting of people and detection of blocked exits or missing safety equipment, designed with privacy and consent in mind.

28Frequently Asked Questions

Q1What is the easiest way to start with Vision AI on Google Cloud?

Try the Cloud Vision API on a handful of your own images. It needs no training, and you can see within minutes whether labels, text or objects answer your question.

Q2Do I need machine learning expertise?

Not for ready-made services or for prompting a multimodal model. Automated training also needs little expertise. Custom model design and tuning benefit from machine learning engineers.

Q3What is the difference between text detection and document text detection?

Text detection is tuned for scattered text in scenes. Document text detection is tuned for dense, structured text such as pages, and returns structure like blocks and paragraphs.

Q4When should I use Document AI instead of plain OCR?

When you need named fields such as invoice number and total, tables or document classification, not just raw text.

Q5Can the face detection feature tell me who someone is?

No. It detects that faces exist and describes visible attributes. Identifying people is a different and sensitive activity requiring careful legal, ethical and consent review.

Q6Can I analyse video?

Yes. Use the Video Intelligence API for stored video and Vertex AI Vision for live streams and video analytics applications. Multimodal models can also answer questions about video clips depending on model support.

Q7How much training data does a custom model need?

It depends on the task and variety, but quality and coverage matter more than raw quantity. Services publish minimum recommendations, and fine-tuning large pretrained models often needs fewer examples. Start small, evaluate, and add data where errors occur.

Q8How do I know if results are good enough?

Build a golden set of representative images with trusted answers, measure precision, recall and error rates, and compare against the cost of mistakes in your business.

Q9Are multimodal models replacing the specialised services?

They overlap and are excellent for flexible tasks and prototypes. Specialised services often remain cheaper, faster and more predictable at high volume, and custom models can be more accurate on narrow tasks. Many solutions combine them.

Q10How is Vision AI billed?

By usage: images per feature, pages, video minutes, running time for streams and endpoints, training hours, and input and output units for multimodal models. Check the current pricing pages for rates and free allowances.

Q11Is my image data used to train Google’s models?

It depends on the service and your agreement. Read the data handling and terms for each service you use, and confirm with your account team or compliance advisers before sending sensitive images.

Q12Can I run models at the edge?

Often yes. Trained models can frequently be exported in lightweight formats for devices, and hybrid designs run quick decisions locally with learning in the cloud. Check the export options of your chosen service.

Q13Why do results sometimes look wrong on my images?

Common causes are poor image quality, unusual content unlike the training data, wrong orientation, or tasks that need specialised knowledge. Improve inputs, test alternatives, and consider custom training for specialised cases.

Q14What is the biggest beginner mistake?

Skipping measurement. Teams that test on a representative sample, define acceptable error rates, keep humans in the loop for doubtful cases and monitor in production avoid most of the costly surprises.

29Summary and Key Takeaways

Vision AI in Google Cloud is a family of services that let applications understand images, documents and video. The Cloud Vision API gives instant labels, text, objects and safe-search results. Document AI turns paperwork into structured fields. Video Intelligence and Vertex AI Vision analyse stored and live video. Custom models on Vertex AI learn your own categories from your labelled images, and multimodal Gemini models answer free-form questions about pictures in natural language. Around them sit the usual cloud building blocks of storage, events, orchestration, warehouses, security and monitoring.

The habits that matter most are simple. Start with the simplest service that could work, measure it on your own representative images, understand confidence and combine automation with human review, validate extracted data, prepare images sensibly, protect personal data with least-privilege access and retention rules, treat faces and fairness with special care, monitor quality and cost in production, and plan to retrain as the world changes. With these in place, a small team can give software a dependable pair of eyes and turn piles of pictures into information people can act on.

Key Takeaways

  • A family, not a single product — ready-made image analysis, document understanding, video analytics, custom models and multimodal models each fit different jobs; confirm current product names and status in the documentation.
  • Climb the ladder — try a ready-made service first, use specialised services for documents and video, prototype flexible tasks with a multimodal model, and train a custom model only when measurements demand it.
  • Data decides quality — accurate, consistent labels, balanced classes, realistic images and diverse coverage matter more than clever algorithms.
  • Results are probabilities — use confidence thresholds, validation rules and a human review zone, especially for decisions that affect people or money.
  • Measure before and after launch — keep a golden evaluation set, track precision and recall for the categories that matter, and monitor drift, quotas and cost in production.
  • Protect people and data — private buckets, least-privilege service accounts, regional choices, retention rules, redaction where needed, and careful, lawful handling of faces and sensitive attributes.
  • Control cost — request only needed features, cascade cheap to expensive models, cache results, process in batches, and shut down idle endpoints and streams.