One City or Two? When an Onward Stop Improves the Trip

A second city should add contrast, not merely another pin on the map.

The decision

Count hotel-to-hotel time, not train time. Checkout, station access, waiting, orientation and check-in can consume half a day. Add the next city when it changes the landscape, food culture or pace enough to justify that cost. Keep one base when both places offer similar experiences or when the first city already has strong day trips.

A better rule

For a week, two well-connected cities can work. For four nights, one city with a deliberate neighborhood change is usually the richer trip.

Explore the relevant CityMustDo collection →

Add contrast, not another checklist

A second city earns its place when it offers a genuinely different landscape, culture or pace and the transfer is reliable. Count packing, station access, check-in and recovery—not just the published journey time. Two nights is often the minimum for a stop that is more than transit.

Protect the first city

Do not split a short trip if the first destination still has several high-priority experiences in distant districts. Add the onward stop when it resolves repetition or creates a logical open-jaw route.

Use a threshold

If the move consumes more than half a usable day or creates a fragile departure, stay put. Compare both cities by trip fit and current transport before booking separate accommodation.

Next step: Use the City Finder to shortlist destinations, then compare the route in the Trip Builder.