Free tool · live demo, rate-limited
Cheapest Month to Fly
Flexible on dates? Stop checking them one by one. Pick a route and a month and see the sampled dates priced side by side. The cheapest day jumps out.
LIS → JFK · November 2026
captured run · 2026-08-2601
$448
02
$398
03
$392
04
$386
05
$386
06
$430
07
$404
08
$435
09
$410
10
$398
11
$398
12
$411
13
$398
14
$411
15
$420
16
$411
17
$404
18
$375
19
$398
20
$381
21
$398
22
$435
23
$398
24
$398
25
$381
26
$386
27
$435
28
$448
29
$447
30
$411
A REAL full 30-day scan: one live request per November departure date, captured on 2026-08-26. Live demo runs sample ~10 dates; this is what a full scan on your own key looks like.
Cheapest day: 2026-11-18 at $375 · Vueling, LEVEL · Google's verdict: typical
How it works
One month, one grid, one obvious answer
1
Pick a route and a month
Airport codes and a month. The scan turns each sampled date into one real search.
2
We scan live, in parallel
Around 10 dates spread across the month, each a real Google Flights search on our key at request time. The demo samples; the API does every day.
3
Read the grid
Each cell is that day’s cheapest live fare. Green is the month’s low end, red its high end, and the cheapest day is called out under the grid.
Who uses it
Anyone whose dates are softer than their route
Flexible travellers
“Sometime in November” is a scan, not thirty searches. Find the cheap pocket of the month, then check that day's live fare and verdict before booking.
Deal sites and newsletters
A monthly grid per route is a publishable artifact. From code, regenerate it on a schedule and flag the days whose verdict flips to low.
Agents and assistants
“Cheapest week to fly this winter” decomposes into exactly this: parallel date searches, compare, answer. The rate limit is what makes the question answerable in seconds.
Found the day? Check the live fare
The grid finds the cheap day; the Flight Price Checker runs that exact date live and shows Google's price band and verdict on the fare.
Scale it
Scanning hundreds of routes? That's what the API is for
A date scan is a burst, not a loop. Serially at one request a second a month is a coffee break; in parallel it is one rate-limit window.
150 / 250 / 500 req/min
By tier (Pro / Ultra / Mega) on the flights API. A 30-date month fits inside one minute on every paid plan.
1 date = 1 request
The same one-way search, fanned out across departure dates with your language's standard parallelism. No special endpoint to learn.
A verdict on every day
Each fare carries Google's price band and low | typical | high verdict where published. Cheap for the month and cheap for the route are different questions, and a scan answers both.
Questions, answered plainly
- Is this scanner really free?
- Yes: no account, no email. Each live scan fires ~10 real searches against live Google Flights data on our own API key, which is why it samples the month instead of pricing all 30 days, and why runs are capped per visitor per day. The page shows a captured full-month scan until you run one.
- Why does the live scan only sample ~10 dates?
- Cost, plainly: every date is a real search on our key. Sampling every ~3 days is enough to see the shape of the month; the full every-day grid is one request per date on your own key. That is what the API is for, and the card under the results shows the exact code.
- What do the colors in the grid mean?
- They are relative to the scanned month only: green sits near the month’s cheapest day, red near its most expensive. It is a within-month comparison, separate from Google’s own low | typical | high verdict, which each day’s cheapest fare also carries when Google publishes it.
- Why do some days show a dash?
- Either Google genuinely returned no itineraries for that date (X-Search-Status: empty, a real answer) or that one search didn’t complete (degraded). The tool shows the status per day instead of inventing a price.
- How would I scan a whole month from my own code?
- One request per departure date, fired in parallel. The flights API allows 150 / 250 / 500 requests per minute by tier (Pro / Ultra / Mega), so a 30-date month finishes in a single burst instead of a serial loop. The code card under the grid is pre-filled with your route.
- Can I scan arrival cities or nearby airports too?
- This tool scans one origin, one destination, one month. From code you can fan out across airports the same way you fan out across dates. It is the same one-request-per-query pattern, just a bigger burst.
The full grid, every day, on your own key
One request per date in one parallel burst, with the price band and verdict judging each fare for you. Free tier on RapidAPI, no card to try.
Free tier: 10 requests/month. No card to try.