Most people open Google Flights, type in their destination, sort by price, and call it a day. Which is fine, I guess, if you enjoy paying $200 more than you need to.
I've been obsessively tracking flight prices for years — including a deeply embarrassing period where I manually checked fares every morning before coffee like some kind of unhinged spreadsheet goblin — and Google Flights is genuinely one of the most powerful free tools out there. The problem is that about 80% of its best features are buried, unlabeled, or just weird enough that most people skip right past them.
Here are eight of them, ranked roughly by how much money they can actually save you.
1. The date grid is not the same as the calendar
This one trips people up constantly. When you search a route, Google Flights shows you a calendar view with prices on each date. That's useful. But the date grid — the actual grid of departure dates vs. return dates — is a completely different beast.
Find it by clicking "Dates" and selecting "Date grid" instead of "Calendar." You'll see a matrix: departure dates across the top, return dates down the side, with fares at every intersection. For a search like JFK to Lisbon (LIS), this grid can show you at a glance that flying out Tuesday April 14 and returning April 28 is $487 round-trip on TAP Air Portugal, while shifting just two days in either direction jumps to $612.
The calendar view makes you check dates one at a time. The grid shows you everything at once. It's the difference between reading a map and asking for directions.
2. "Explore" mode is basically a deal discovery engine
If you have flexibility on destination — or you want to pretend you do until a genuinely stupid-cheap fare convinces you otherwise — the Explore map is where you should start.
Go to Google Flights and click "Explore" instead of entering a destination. You'll see a world map with price bubbles floating over cities. Set your origin (say, ORD), your rough travel dates, and watch the map populate. Right now in early 2026, I can see ORD to Reykjavik (KEF) sitting at $389 round-trip on Icelandair, ORD to Mexico City (MEX) at $241 on Aeromexico, and ORD to Tokyo (NRT) at $678 on ANA — all in one view, no tab-switching required.
The filter panel on the left lets you restrict by trip length, which is the killer feature here. Set "1 week" and you'll only see fares that work for a 7-day trip. Set a max price of $500 and watch the map reorganize around what's actually reachable. It's not perfect — it sometimes surfaces fares that disappear when you click through — but as a starting point for "where should I even go," nothing beats it.
Pro Tip: Explore mode updates in near-real-time, but the prices shown are estimates until you click through to the full search. Always verify before getting too attached to a number.
3. The price tracking alert (that most people set up wrong)
Yes, Google Flights has price alerts. Most people know this. Most people also set them up in a way that makes them nearly useless.
The common mistake: setting an alert for a specific round-trip itinerary with fixed dates. That's fine, but you're essentially asking Google to notify you when one very specific thing gets cheaper. What you actually want is to track a route over a date range.
Search your route with flexible dates, then look for the "Track prices" toggle at the top of the results. When you turn it on without committing to specific dates, Google will alert you to price movements across the whole route — not just your one combination. You'll get an email when LAX-BCN drops broadly, not just when your exact April 22-May 6 itinerary ticks down $4.
Pair this with FlightKitten's pounce alerts and you've got genuine redundancy: Google catches the slow drift, FlightKitten catches the flash sales that evaporate in hours. I've found that neither service catches everything the other one does, which is mildly annoying but also just how it works.
4. Filtering by carry-on bag included
This one is so obviously useful that I'm still baffled it took Google years to add it.
Basic economy fares on carriers like American, United, Delta, and Spirit often appear cheaper in search results but include zero bags — not even a carry-on in some cases. You book what looks like a $189 flight from BOS to MIA, then pay $99 in bag fees and end up wishing you'd just paid $249 for the main cabin fare that included your bag.
In the filters panel (click "Bags" or look under "More filters"), you can now filter to show only fares that include a carry-on. The price comparison becomes honest immediately. On a recent BOS-MIA search, filtering for carry-on included knocked Spirit off the first page entirely and surfaced a JetBlue Blue Basic fare at $214 that was actually cheaper all-in than Spirit's $189 base.
Do this every time. It takes four seconds and it will save you from at least one rage-inducing bag fee surprise per year.
5. The "stops" filter has a secret third option
Everyone knows you can filter for nonstop flights. Fewer people know you can filter for "1 stop or fewer" — which is the actually useful setting.
Here's why: nonstop filters are great when you're paying for speed and convenience. But on long-haul economy routes, a one-stop itinerary can be $200-400 cheaper than nonstop and only add 2-3 hours to your journey. The problem is that "any number of stops" clutters results with awful three-stop itineraries routed through places that make no geographic sense.
"1 stop or fewer" is the sweet spot. You keep the cheap connecting options — like that $541 SFO to Rome (FCO) on Lufthansa via MUC that beats the $789 United nonstop — without wading through the chaos of multi-stop budget routing.
Find it under "Stops" in the filter bar. It's the middle option. Use it.
6. Separate ticket warnings (read them)
This one isn't a money-saving trick so much as a money-losing prevention trick.
When Google Flights assembles a cheap itinerary using flights from two different airlines that aren't booked together, it shows a small "Separate tickets" warning. Most people gloss over this. Don't.
A separate ticket itinerary means if your first flight is delayed and you miss the connection, the second airline owes you exactly nothing. No rebooking, no hotel, no sympathy. You're buying two independent one-way tickets that happen to be scheduled back-to-back.
I learned this the hard way on a split-ticket routing through Reykjavik in 2023. The Icelandair leg was delayed 90 minutes, I missed the WOW Air successor connection, and I spent a genuinely miserable night in KEF airport eating a $22 airport sandwich and questioning my life choices. The $140 I saved on the split ticket did not cover the replacement fare.
If you're going to book separate tickets anyway — sometimes the savings are worth it — at minimum add a 3-hour buffer between flights and buy travel insurance that covers missed connections. Google won't stop you, but at least you'll know what you're agreeing to.
7. The price history graph
This feature is criminally underused and it's right there in the interface.
When you're looking at a specific route and date combination, scroll down past the main results. You'll see a "Price history" section showing a graph of what this route has cost over the past several months. This is not a forecast — Google will tell you whether current prices are "low," "typical," or "high" relative to historical data.
On a recent search for DFW to London Heathrow (LHR) in late May, the price history showed fares averaging $820-940 over the prior 90 days. The current fare was $743 on British Airways. Google flagged it as "low." That's genuinely useful context that turns "should I book now or wait" from a gut-feel decision into something resembling a data-driven one.
It's not infallible — historical prices don't guarantee future prices, especially around holidays or when airlines adjust capacity — but it's a much better signal than nothing.
Pro Tip: The price history graph is most reliable on well-traveled routes (transatlantic, transpacific, major domestic corridors). On thin routes with few flights per week, the historical data is sparse enough to be misleading.
8. Multi-city search for open-jaw routing
If you're doing any trip longer than a week, you should at least check whether an open-jaw itinerary saves you money. An open-jaw means flying into one city and out of another — fly into Paris, travel overland, fly home from Rome. Google Flights handles this natively through the "Multi-city" option, and it's almost always cheaper than booking two separate one-ways.
Here's how to find it: on the main search page, click the dropdown that says "Round trip" and switch to "Multi-city." You can now build a custom routing. Enter JFK-CDG for leg one, then FCO-JFK for leg two, set your dates, and search. The results will show you combined pricing across carriers — sometimes mixing and matching Air France on the outbound with ITA Airways on the return, for instance.
A real example from a search I ran last month: JFK to Paris inbound + Rome to JFK outbound came in at $697 combined on a mixed Air France/ITA itinerary. Two separate one-ways for the same routing? $891 total. The multi-city search found $194 in savings by treating the whole trip as one booking.
The catch is that multi-city results are slower to load and sometimes miss the cheapest combinations. Run the search, note the price, then cross-check against booking each leg separately on the airline's own site. Sometimes splitting it is still cheaper. But you won't know until you check both.
| Search method | JFK-CDG + FCO-JFK example | Notes |
|---|---|---|
| Multi-city (Google Flights) | $697 | Mixed carrier, one booking |
| Two separate one-ways | $891 | More flexibility, higher cost |
| Round-trip JFK-CDG only | $612 | Doesn't include Rome departure |
The one thing Google Flights still can't do
For all its power, Google Flights doesn't catch every fare. It's weak on budget carriers that don't share data (Ryanair being the obvious European example), and it's genuinely bad at surfacing flash sales that last 6-12 hours before the airline quietly pulls them.
That's the gap that FlightKitten's hunts are built for — you set a catch on a route you care about, and when something weird and cheap shows up, you get a pounce alert before it disappears. Think of Google Flights as your research layer and FlightKitten as your early warning system. They're solving different parts of the same problem.
Start with the date grid, end with the price history
If you take nothing else from this: open the date grid before you commit to dates, and check the price history before you commit to booking. Those two habits alone will change how you use Google Flights.
The other six features are worth knowing, but those two are the ones that will actually shift your behavior in a measurable direction. Everything else is optimization. The date grid and price history are fundamentals that most people skip entirely.
Now go set up a hunt for that route you've been vaguely thinking about for six months. The fare won't wait for you to feel ready.
