Google Veo 3.1

Google’s cloud video generation and editing model family, with text/image-to-video, audio and editing controls.

Score calculation

(6 + 3 + 3 + 2 + 7 + 3) ÷ 6 = 4.0

Pressure target: −1 overall point. Overall score: 3.0/10.

6 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Google Veo 3.1: cloud access. Available through Gemini, Flow and developer routes; plan and per-generation pricing vary by route. Ratings describe the stated product, company or configuration in each finding.

What fits your needs

Google Veo 3.1 cloud model accessed through Gemini, Flow or developer products; feature and billing route differs by surface.

Tasks

Text/image-to-video generation, audio and editing are available through different Google surfaces; supported duration and controls depend on route/model.

See the evidence

Billing

Consumer plan access and developer API usage have separate limits and billing; check the exact app or API route before estimating cost.

See the evidence
Tradeoffs to expect

Route

Veo is cloud inference; consumer Gemini/Flow and developer API requests have distinct account, privacy and usage rules.

See the evidence

Provenance

Google says generated media can include SynthID; verification can fail to identify other providers and doesn’t confirm consent or truth.

See the evidence
How to switch

Get started

Choose Gemini, Flow or the Gemini API, then check that route's model availability, account eligibility and current usage terms before moving assets.

See the evidence
Practical questions

Age and sensitive content

Google’s generative-AI policy prohibits CSAM, NCII, explicit sexual content and deceptive impersonation; Gemini account age rules and feature access vary by country and route.

See the evidence

Likeness and input rights

Policy prohibits using personal data/biometrics without legally required consent and non-consensual intimate imagery. Applies to covered Google routes; confirm the app/API terms for the selected surface.

See the evidence

Labels and verification

Google documents SynthID and Content Credentials verification for supported media; non-detection does not rule out other AI origins and credentials do not prove truth or consent.

See the evidence

Commercial use

Terms depend on the route and account. Google’s generative AI policy is not a blanket copyright warranty or indemnity.

See the evidence

Energy practices

6/10↑

Google provides company-wide data-center energy and clean-energy metrics. Flow lets users select Veo tiers and video duration/features, but publishes no Veo-specific footprint.

See the evidence

Google provides company-wide data-center energy and clean-energy metrics. Flow lets users select Veo tiers and video duration/features, but publishes no Veo-specific footprint. The score describes documented measurement transparency and available controls, not environmental performance.

1 + 2 reporting + 1 electricity + 2 controls = 6/10. This grade covers documented practices and transparency; it does not measure the energy or emissions of a request.

Company-wide electricity and carbon-free-energy figures are not attributed to Veo 3.1, a region, or a single video. Credits track billing, not energy; the reported 66% clean-energy share is partial and not a product-level guarantee.

Reporting2/3
Google’s 2025 Environmental Report publishes dated company data-center energy, emissions, and clean-energy metrics with stated scope and methodology. It is not allocated to Veo, so D2 is the cap.
Electricity sourcing1/3
Google reports a 66% company-wide carbon-free-energy share in 2024 on an hourly basis. It is partial corporate evidence without Veo region/site allocation or independent verification, so it earns E1 only.
Resource controls2/3
Flow documents Lite/Fast/Quality model selection, 4/6/8-second clip durations, supported feature selection, resolution options, and the ability for one request to generate two videos. These controls bound output/request shape, but physical savings are unmeasured.

Water disclosure

Google reports that its water stewardship projects replenished approximately 7.7 billion gallons in 2025, about 78% of its 2025 freshwater consumption. The company-wide figure is not a measurement of Gemini, Vertex AI, or a particular request.

Google-reported 2025 corporate operations and replenishment. The page does not allocate water consumption to a product, model, region-specific request, or inference workload.

Training data

3/10↑

Google’s Veo card says the model used audio, video and image data with captions and safety, compliance, quality and deduplication filtering. It does not name datasets, licenses or creator controls.

See the evidence

The public card gives modality and processing details but no source list or permissions evidence for the assessed base. Google’s general data-governance statement is contextual policy, not a release-level license audit.

1 + 1 source transparency + 1 permission + 0 creator controls = 3/10. This grades documented training-data safeguards, not a legal ruling.

Exact Veo 3.1 consumer route, training-source identities, source-level permissions and rights-holder controls are not disclosed.

Source transparency1/3
The card names modalities, captioning and filtering but not source datasets.
Documented permission1/4
Google states a general process for reviewing sources and licenses, but Veo-specific permissions remain unitemized.
Creator controls0/2
No training-source exclusion or removal process is established by the reviewed model disclosures.
Data-rights rubric ↗

Your data & privacy

3/10↑

For Veo accessed through consumer Gemini Apps, prompts and shared media can be saved with Keep Activity on, used to improve/train Google services, and some reviewed data retained for up to three years. Turning activity off avoids model-improvement use for future chats absent feedback, though chats remain for 72 hours.

See the evidence

The consumer route permits broad activity reuse by default but publishes controls that reduce it. This score applies only to Gemini Apps consumer use; Google Flow, API, and enterprise routes have separate terms and are not rated here.

Openness

2/10↑

Veo is a hosted Google service; model weights and full training pipeline are not publicly released in the reviewed product materials.

See the evidence

This rating describes access to the model itself. Developer APIs provide an interface but do not make the underlying weights inspectable or movable.

Worker protections

7/10↑

Google has a supplier-responsibility system with worker surveys, third-party audits and grievance access, alongside current worker reports describing pay, pace and support concerns among AI raters.

See the evidence

Google says its Supplier Code applies to supplier and staffing-partner work, extended workers can report concerns anonymously through Google’s helpline, and its 2026 FY2025 report describes supplier audits and worker surveys with follow-up. Separately, Alphabet Workers Union-CWA’s 2025 report and raters’ pay-parity letter describe low pay, benefits gaps, insecure contracts and inadequate task-time; The Guardian documented raters’ accounts of rapid task timing, distressing moderation work and limited mental-health support, while Google says suppliers employ these workers and set their employment terms. The company system merits credit, but findings from hardware/supplier programs do not prove every AI rater is covered or remedied.

1 + 2 pay & conditions + 2 worker voice & remedy + 2 evidence & follow-through = 7/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The FY2025 supplier program is risk-prioritized and does not disclose whether its survey/audit cohort included GlobalLogic AI raters; Google’s own policy places wage/benefit setting with suppliers. Worker reports are specific but are not an adjudicated finding about every supplier or rater.

Pay & conditions2/3
Supplier standards and vetting apply to extended workforce and current AI-rater testimony documents concrete working conditions, but rates, coverage and implementation vary by supplier and some worker evidence is self-reported.
Worker voice & remedy2/3
Extended workers have access to Google’s anonymous helpline and supplier feedback channels; union organizing and direct worker reports document voice, though they also describe limited influence over conditions.
Evidence & follow-through2/3
Google reports third-party supplier audits, worker surveys, follow-ups and program improvements; these are company-reported and the published figures don’t confirm coverage of AI annotation contractors specifically.
Workers rubric ↗

Military ties

3/10Broad defense ties↑

Google has a current DoD AI/cloud contract and has demonstrated military training/exercise support, but the reviewed evidence doesn’t confirm combat targeting or strike-intelligence deployment.

See the evidence

Google Public Sector describes a $200 million ceiling DoD CDAO contract and access to AI/cloud capabilities, including classified environments. Its Mobility Guardian 2025 account describes an Air Force exercise/edge workflow processing air-defense data and generating insights for counter-UAS triggers; this is exercise and support evidence, not proof that Google AI selected targets or supplied combat intelligence in an actual operation. Google’s current AI Principles include human oversight and safety commitments but no categorical military-use prohibition. The broad DoD contract leaves substantial enablement potential, so classify as broad-defense and apply the cap; do not call the exercise direct combat use.

1 + 0 use restrictions + 1 enforcement & oversight + 2 relationship disclosure = 4, capped at 3/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.

Public sources do not disclose all task orders, operational use outcomes, customer-enforceable use restrictions, or independent oversight. The specific models and releases used in every defense workflow are not established.

Use restrictions0/4
The current AI Principles reviewed don’t confirm a binding weapons or harmful-surveillance prohibition for defense contracts; the older 2018 weaponization commitment is not current evidence.
Enforcement & oversight1/3
Google’s public AI Principles describe human oversight and safety practices but do not disclose military-specific independent review, enforcement, or remedies.
Relationship disclosure2/2
Google names the CDAO contract, its ceiling and the Mobility Guardian exercise workflow; the named public materials disclose no actual combat mission or current contract-level safeguards.

Google documents a broad DoD AI/cloud contract and military exercise support, but no confirmed operational use for target selection, strikes, or combat intelligence. Broad-defense cap applies. The relationship limits this grade to 3/10.

Military rubric ↗

BDS targets

Pressure target↑

Google is named as a pressure target in the BNC campaign sources.

See the evidence

Google is named by the BNC as a pressure target. BDS campaign sources state their own position; this classification does not assess the product or independently adjudicate the underlying claims.

All sources

Side by side