Free tool
Parking price calculator: find your optimal hourly rate
Last updated: . Every calculation runs entirely in your browser; nothing is sent to our servers unless you opt in to email your result.
The economics behind 'right price' for parking
Pricing parking is fundamentally a yield-management problem similar to airline seats and hotel rooms. Every space-hour is a perishable inventory item — once the hour passes, that potential revenue is gone forever. The goal of pricing is not to maximize the price-per-occupied-space; it's to maximize the revenue-per-space-hour, which is price × occupancy.
Mathematically, for a lot with constant-elasticity demand, revenue per space-hour is maximized when the marginal-revenue curve crosses zero. With elasticity between 0.3 and 0.7 (typical for parking), this happens at occupancy near 80-85%. Below that, demand is inelastic in the operational sense — you can raise rates without losing meaningful occupancy. Above that, demand becomes elastic — small rate increases lose more occupancy than the rate gain captures.
How the calculator solves for the optimal rate
The calculator uses the constant-elasticity demand equation: occupancy / target_occupancy = (current_rate / new_rate)^elasticity. Solving for new_rate gives the rate that would shift occupancy from the current observed level to the target (85% by default). The result is then quantized to the nearest $0.25 because drivers don't respond to sub-quarter precision and quarter rates are easier to communicate.
The projected new occupancy under the recommended rate is computed by inverting the equation. In most cases it lands close to 85%, with small deviations when the quantization moves the rate further from optimal than the underlying math suggested. If your inputs would require a rate below $1 or above $15, the calculator clips to those bounds — outside that range the constant-elasticity assumption breaks down.
The revenue lift figure is the percentage change in price × occupancy comparing current to recommended. This is the single best metric to focus on because it accounts for the trade-off between rate and volume. A recommended rate that raises price 15% but drops occupancy 10% has a lift of about +3% — small, positive, but not necessarily worth the operational disruption.
When to follow the calculator vs. ignore it
Follow it when the recommended rate change is between +5% and +25% versus current. This is the band where the model is most reliable and the operational risk of being slightly wrong is small. Implement the change for one full month, observe actual occupancy and revenue, and re-run the calculator with the updated occupancy.
Ignore it when the recommended change exceeds 25% in either direction. A 25%+ change suggests either a wrong elasticity input or a structural change (new competitor, new development, regulation) that makes the constant-elasticity model invalid. Run a small test (one weekend, one day-part) before committing to the full change.
Override it when there's a strong strategic reason. Promotional pricing during a competitor's closure, predatory pricing to capture a competitor's loyal regulars, or municipal pricing constraints all justify deviating from the model output. Document the override reason so future operators can re-evaluate it.
Communicating a price change to drivers and stakeholders
The mechanical part of a price change is updating signage and the QR-payment surface — typically less than a day's work. The harder part is communication. Three audiences need different messages.
Regular drivers. Post the new rate at least 30 days before it goes live, with the explanation framed around demand ("rates adjusted to keep spaces available during peak hours") rather than cost ("rates raised to cover expenses"). Demand framing tests significantly better in driver surveys.
Property owner / partner. Send a one-page brief showing the recommended rate, projected revenue lift, and the calculator's sensitivity to elasticity assumptions. Most owners accept rate increases backed by data; the friction comes from rate increases that look arbitrary.
Municipal authority (if regulated). Submit the rate change well ahead of any required public-comment period. Include the elasticity methodology, comparable lot benchmarks, and a commitment to revisit if observed occupancy doesn't stabilize at the target. Regulators respond well to transparent methodology.
Related tools and pricing resources
- Dynamic pricing calculator — once you have an optimal anchor rate, vary it by time of day for additional lift.
- Revenue calculator — model gross monthly and annual revenue at the recommended rate.
- Demand estimator — for greenfield sites where you don't yet have current occupancy data to feed into this calculator.
- Parking revenue optimization guide — academic background on elasticity, the SFpark experiment, and yield management for parking.
Ready to turn this estimate into real revenue?
Print a QR sign, post it at your lot, and start accepting payments today. The Starter plan is free forever.
FAQ — Parking Price Calculator
- How do I find the optimal parking rate?
- The optimal hourly rate is the one where occupancy stabilizes around 80-85%. Below that, you're underpriced — the lot fills early and turns drivers away. Above that, you're overpriced — drivers go elsewhere and the lot sits half-empty. The calculator above solves the constant-elasticity demand equation for the rate that targets 85% occupancy given your current rate, current occupancy, and elasticity assumption.
- What's the difference between this and the dynamic pricing calculator?
- This calculator finds a single optimal flat rate — useful when you can only set one rate or you're testing a rate change for next month. The dynamic pricing calculator finds different rates for different time slots — useful when your platform supports time-of-day pricing. Most operators use this calculator first (find the right anchor rate) and then the dynamic calculator (vary around the anchor).
- How is demand elasticity measured?
- Elasticity is the percentage change in demand divided by the percentage change in price. If you raised the rate 10% and occupancy fell 4%, elasticity = 0.4. The cleanest measurement comes from a deliberate A/B test: pick two similar weeks, change the rate by 15% in week two, measure occupancy delta. Most operators don't run formal tests and instead use industry benchmarks: 0.2-0.4 commuter, 0.4-0.7 mixed-use, 0.7-1.2 event/destination.
- Why target 85% occupancy specifically?
- Empirically, 85% is the sweet spot where you've extracted near-maximum revenue per space-hour without rejecting customers. Below 80%, raising the rate increases revenue per filled space faster than it loses occupancy. Above 90%, you're routinely turning paying customers away. The 85% target was popularized by Donald Shoup's 'High Cost of Free Parking' and validated in the SFpark study, which found revenue maximized at 80-85% occupancy across nearly every block tested.
- Should I match my competitor's rate?
- Match within ±10% if you're undifferentiated. Above that, customers shop on price and you bleed share. Price 15-25% above competitors only if you have a quality advantage drivers can verify (better location, security, lighting, amenities). Price 15-25% below competitors deliberately if you want to capture price-sensitive volume — but verify your operational margins can absorb the lower rate first.
- What happens if my elasticity guess is wrong?
- If you guess too low (think drivers are stickier than they are), the calculator recommends an aggressive rate increase that empties the lot. Recovery: drop back to old rate within 1-2 weeks. If you guess too high (think drivers are more sensitive than they are), the calculator recommends a conservative rate that leaves money on the table. Recovery: try a smaller rate increase next month and observe. The asymmetric risk justifies starting conservative.
- How often should I re-run this calculator?
- Quarterly for a stable lot, monthly for a lot in transition (recently switched platforms, new nearby development, seasonal swings). The right cadence is whichever frequency matches how often your inputs change meaningfully. If competitor rates haven't moved and your occupancy is steady, the recommended rate won't change much month to month.
- Can I use this to set monthly contract pricing?
- Indirectly. Compute the recommended hourly rate, multiply by the typical contract usage (~120 paid hours/month for a weekday-only office contract), and use that as your monthly contract floor. Most operators discount monthly contracts by 30-50% from the implied transient rate to lock in predictable revenue. The calculator gives you the anchor; your discount policy gives you the contract price.
- Is the recommended rate the price drivers will see?
- Yes if you're on a flat-rate setup. With dynamic pricing enabled, the recommended rate is the baseline around which time-of-day rates vary. Park Graph's pricing engine uses the calculator's output as the anchor and then adjusts ±25% by time slot using the dynamic-pricing calculator's logic.