LLMgoogle

Google: Gemini 3.6 Flash (batch)

Gemini 3.6 Flash is a high-efficiency model from Google for coding, agentic workflows, and web and app development. It is designed to produce polished outputs with fewer unnecessary edits and...

Anyone in the Project can @-mention Google: Gemini 3.6 Flash (batch) with the team's shared context - pooled credits, one chat, one memory.

All models

Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.

Verdict

Gemini 3.6 Flash Batch trades real-time response for dramatic cost savings — $0.38 per million input tokens makes it one of the cheapest multimodal models available. The 1M token context window handles book-length documents, and batch processing suits workflows where you can wait minutes or hours for results. Reach for this when you're processing large volumes of text, images, video, or audio and latency isn't a constraint. Skip it for interactive applications or anything requiring sub-second responses.

Best for

  • Bulk document analysis with deferred results
  • Cost-sensitive video transcription jobs
  • Large-scale image classification pipelines
  • Overnight processing of audio libraries
  • Budget-conscious long-context summarization

Strengths

The pricing structure is the standout — at $0.38 input and $1.88 output per Mtok, this undercuts most competitors by 60-80% for batch workloads. The 1M token context window accommodates entire codebases or multi-hour video files without chunking. Multimodal support across text, image, video, and audio means you can process mixed-media datasets in a single pass. Batch mode eliminates rate limits, so you can queue thousands of requests without throttling concerns.

Trade-offs

Batch processing introduces latency — expect minutes to hours for results depending on queue depth, making this unsuitable for user-facing applications. We lack public benchmark data, so performance relative to Claude or GPT-4 on reasoning tasks remains unverified. The Flash architecture typically sacrifices accuracy for speed, and batch mode doesn't change that fundamental trade-off. Video and audio processing quality is unproven without published evals. No streaming means you can't monitor progress or cancel mid-job.

Specifications

Provider
google
Category
llm
Context length
1,048,576 tokens
Max output
65,536 tokens
Modalities
text, image, video, file, audio
License
proprietary
Released
2026-07-21

Pricing

Input
$0.38/Mtok
Output
$1.88/Mtok
Model ID
google/gemini-3.6-flash:batch

Per-token prices show what the model costs upstream. On Switchy your team draws from one shared org credit pool - one plan, one balance for everyone.

Team cost calculator

Estimated monthly spend
$14.52
17.6M tokens / month
5 seats · 80 msgs/day

Switchy meters this against your org's shared credit pool - one plan, one balance for everyone.

Providers

ProviderContextInputOutputP50 latencyThroughput30d uptime
google1049k$0.38/Mtok$1.88/Mtok———

Performance

Performance snapshots are collected daily. Check back after the next ingestion run.

Benchmarks

Public benchmark scores are not available yet for this model. Check back after the next ingestion run.

Works well with

Top MCPs

Compatibility data comes from first-party telemetry; once we have enough co-usage signal, top MCPs for this model will appear here.

How Switchy teams use it

Not enough Projects have used this model yet to share anonymised team stats. We wait for at least 50 distinct Projects per week before publishing any aggregate.

Starter prompts

Batch Transcribe Videos

Transcribe all spoken dialogue in this video. For each scene change, provide a one-sentence visual description. Format as timestamped entries: [MM:SS] dialogue or [MM:SS] SCENE: description.

Classify Image Archive

Classify this image into exactly three categories from: product, person, landscape, document, diagram, screenshot, food, animal, vehicle, interior, other. Return only the three category names, comma-separated, most-relevant first.

Summarize Long Documents

Read this entire document and provide a 300-word executive summary. Focus on key arguments, supporting evidence, and conclusions. Identify any internal contradictions or gaps in reasoning.

Extract Audio Metadata

Listen to this audio file and extract: 1) number of distinct speakers, 2) primary topics discussed with timestamps, 3) any action items or decisions mentioned, 4) overall tone (formal/casual/technical). Format as JSON.

Analyze Code Repositories

Review all files in this repository. Identify: 1) architectural patterns used, 2) potential security vulnerabilities, 3) code quality issues (duplication, complexity), 4) missing documentation. Prioritize findings by severity.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

Analyze this 45-minute product demo video and extract a structured summary: key features shown, timestamps for each demo segment, and any technical limitations mentioned by the presenter.

Output

The model would produce a hierarchical breakdown: an executive summary paragraph, followed by a timestamped table of demo segments (e.g., '03:42 - Dashboard navigation, 12:18 - API integration walkthrough'), then a bulleted list of 8-12 features with brief descriptions, and finally a short section on limitations discussed around the 38-minute mark. The structure would be clean and scannable, with precise timestamp references that match the video's actual content.

Notes

Showcases the 1M+ token context window handling long-form video input. The batch processing mode makes this economical for bulk video analysis tasks. However, real-time use cases requiring sub-second latency would need the standard Gemini Flash variant instead.

Prompt

Review this 200-page technical specification PDF for our aerospace client. Flag any sections that conflict with DO-178C software certification requirements and suggest specific remediation steps.

Output

The model would return a compliance report identifying 6-8 conflict areas, each with: the conflicting spec section number, the relevant DO-178C clause, a plain-English explanation of the mismatch, and 2-3 concrete remediation options ranked by implementation effort. For instance, it might flag insufficient traceability documentation in Section 4.7 against DO-178C Table A-3, then suggest either enhancing the existing matrix or adopting a requirements management tool.

Notes

Demonstrates multimodal file processing with domain-specific reasoning. The $0.38/Mtok input pricing makes large document analysis viable at scale. Trade-off: batch mode introduces processing delays (typically minutes to hours), so this suits overnight report generation rather than interactive document Q&A.

Prompt

Generate a Python data pipeline that ingests these 12 CSV files, normalizes timestamps across UTC and PST entries, joins on customer_id, then outputs a single Parquet file partitioned by month. Include error handling for malformed rows.

Output

The model would produce a ~150-line script using pandas and pyarrow, with: a configurable file-path list, timezone conversion logic using pytz, an outer join strategy with explicit handling of null customer_ids, try-except blocks that log malformed rows to a separate error CSV, and partitioned write logic that creates monthly subdirectories. The code would include docstrings and inline comments explaining the UTC/PST normalization approach.

Notes

Highlights code generation with multi-file context awareness. The massive context window lets you paste all 12 CSV schemas directly into the prompt. The batch pricing model ($1.88/Mtok output) keeps costs low even for verbose, well-commented code. However, you won't get iterative refinement in real-time — submit the job, then review the complete output later.

Use-case deep-dives

Overnight batch document processing

When batch pricing makes multimodal extraction worth it at scale

A 12-person compliance team processes 800 mixed-format client submissions every night—PDFs with tables, scanned forms, video depositions with timestamps. Gemini 3.6 Flash batch mode cuts input cost to $0.38/Mtok, which matters when you're feeding 200k+ token documents through OCR-free extraction. The 1M token context window means you can drop an entire case file (contracts, emails, video transcripts) into one prompt and ask cross-reference questions without chunking. Output at $1.88/Mtok stays reasonable because you're generating structured JSON, not long-form prose. If your documents average under 50k tokens or you need sub-5-second turnaround, standard Flash is the better call. For overnight jobs where latency doesn't matter and volume is high, batch mode pays for itself after 200 documents per month.

Video content moderation pipeline

Native video input for high-throughput safety review

A 4-person trust and safety team at a UGC platform reviews 1,200 flagged videos per day—each 30-90 seconds, mix of user reports and automated flags. Gemini 3.6 Flash batch accepts video natively, so you skip the transcription step and the model can catch visual context (gestures, on-screen text, scene changes) that audio-only models miss. At $0.38/Mtok input, processing a 60-second video with scene analysis costs roughly $0.02-0.04 depending on resolution. The batch queue adds 10-15 minutes of latency, which works fine for overnight review cycles but breaks real-time moderation. If you need decisions in under 60 seconds, you're stuck with standard Flash at 2.5x the input cost. For daily batch review where visual context matters and you're processing hundreds of videos, this is the cheapest multimodal option that doesn't require preprocessing.

Weekly financial report generation

Long-context synthesis when turnaround time isn't critical

A 3-person finance team at a Series B startup compiles board decks every Friday—pulling from 40+ data sources (Stripe exports, bank statements, HubSpot CSVs, Notion meeting notes). Gemini 3.6 Flash batch handles the 1M token context window, so you can load the entire week's raw data and ask for variance analysis, trend summaries, and anomaly flags in one prompt. At $0.38 input and $1.88 output per Mtok, a 300k token input with 8k token output runs about $0.13 per report. The batch queue adds 20-30 minutes, which is fine for a Friday morning job that doesn't ship until afternoon. If you need same-hour turnaround or you're generating reports more than twice a week, standard Flash justifies the 2.5x cost bump. For weekly synthesis jobs where you're trading latency for cost and context depth, batch mode is the obvious pick.

Frequently asked

Is Gemini 3.6 Flash batch good for processing large document sets?

Yes, with a 1M token context window, Gemini 3.6 Flash batch handles entire codebases, legal document collections, or research paper archives in a single request. The batch mode trades latency for cost, making it ideal for overnight processing jobs where you're analyzing hundreds of files. If you need real-time responses, use the standard Flash endpoint instead.

Is Gemini 3.6 Flash batch cheaper than Claude for bulk processing?

At $0.38 input per Mtok, Gemini 3.6 Flash batch undercuts Claude 3.5 Haiku ($0.80) and Sonnet ($3.00) for input tokens. Output at $1.88/Mtok is competitive with Haiku's $4.00 but higher than GPT-4o mini. For batch jobs where input volume dominates—like classification or extraction—this is the cheapest frontier model option.

Can Gemini 3.6 Flash batch process video and audio files?

Yes, it accepts video, audio, images, and files alongside text. This makes it useful for transcription pipelines, video content moderation, or multimedia dataset labeling. The 1M context window means you can include multiple video clips or hours of audio in one request, though processing time scales with content length in batch mode.

How does Gemini 3.6 Flash batch compare to the standard Flash model?

Same capabilities and context window, but batch mode queues requests for asynchronous processing—typically completing within hours rather than seconds. You get a 50% discount on both input and output tokens in exchange for that latency. Use batch for nightly ETL jobs, dataset labeling, or bulk content analysis where immediate results aren't required.

Should I use Gemini 3.6 Flash batch for production API endpoints?

No. Batch mode is asynchronous with unpredictable completion times, making it unsuitable for user-facing features or real-time workflows. Use it for background jobs: nightly report generation, training data preparation, or scheduled content audits. For anything customer-facing, stick with the standard Flash endpoint or a synchronous model.

Compare with

More language models

See all language models →

Data last verified 13 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.