Gross per mile
$4.00/mi
Gross payout divided by modeled weekly miles.
San Francisco, CA | Updated Jul 2026
Uber San Francisco Pay Per Mile $19.93/hr Net
Use this when the real question is whether the offers clear a dollar-per-mile floor.
Net hourly
$19.93
Gross weekly
$1105
Miles/week
276
Hours/week
38
Evidence profile
San Francisco Uber Pay Per Mile evidence check
Indexed because it has 3 cited local sources and a city-specific calculation model; driver reports are shown when available.
Unique data anchor: The offer floor is computed from $1105.00 weekly gross over 276 modeled miles, then checked against net hourly.
Cited sources
3
Driver reports
3
City-specific
0
Method
city-rich-v4.0
Checked 2026-02-26
Direct answer
Uber San Francisco per mile estimate
The Uber San Francisco side-hustle baseline uses $1105/week gross over 276 miles, then converts the result into $19.93/hr net after mileage and tax assumptions.
For drivers, the practical question is not only hourly pay. A shift can look good by the hour and still fail a dollar-per-mile floor if it sends you across zones, into deadhead miles, or back home unpaid.
Local operating context
What changes the pay per mile math in San Francisco
San Francisco should be treated as multiple micro-markets: Mission, SoMa, and North Beach can convert well while US-101, I-280, and Embarcadero approaches can consume margin through deadhead.
In San Francisco side-hustle mode, prioritize Mission, SoMa, and North Beach, cap transfer distance on US-101, I-280, and Embarcadero approaches, and route fallback through Inner Sunset and Richmond whenever conference weeks and Giants home games introduces conversion noise.
Conversion drop when leaving Mission, SoMa, and North Beach
Route friction on US-101, I-280, and Embarcadero approaches
parking tickets and hill-driven efficiency loss
“My side-hustle rule is simple: protect a 20-dollar floor, keep the map tight near Mission, SoMa, and North Beach, and switch once to Inner Sunset and Richmond before ending a weak block.”
“At 25-hour schedules, the winners are usually the people with weekly records and reserve discipline. Process quality matters more than optimism.”
Goal math
San Francisco Uber target calculator
The useful answer is not only pay per hour. It is how many real hours and miles the target requires.
| Target | Modeled hours | Modeled miles | Gross needed | Best use |
|---|---|---|---|---|
| $100 net day | 5.0 hrs | 36 mi | $146 | Dinner, weekend, or two short peaks. |
| $200 net day | 10.0 hrs | 73 mi | $292 | Long stretch goal; compare against fatigue and dead miles. |
| Per-mile floor | 38 hrs/wk | 276 mi/wk | $4.00/mi | Reject offers that look busy but fail after route miles. |
Data-backed checks
Pay Per Mile metrics for San Francisco
Net profit per mile
$2.78/mi
Net profit after mileage and tax assumptions divided by modeled weekly miles.
IRS mileage proxy
$0.725/mi
A benchmark for vehicle operating cost pressure in 2026.
Evidence patterns
What the source data says to check
These cards turn driver discussions, official pay docs, field tests, and large driver datasets into the specific checks this page is trying to answer.
Acceptance floor
Drivers compare offers by mile before hourly math
Uber San Francisco is modeled at $4.00 gross/mi and $2.78 net/mi. That mirrors driver-source behavior: screen weak offers by dollars per mile before trusting an hourly total.
Source: Uber driver $/mile discussion →Cost benchmark
A good offer still has to clear vehicle-cost pressure
The same $0.725/mi IRS proxy used across the site gives this page a hard comparison line. If the offer barely beats the cost proxy, the gross payout is not enough.
Source: IRS 2026 mileage rate →Winner pattern
Top pSEO pages make the query-specific comparison visible
Good pSEO examples expose the exact data point the searcher came for. Here, the page puts gross-per-mile, net-per-mile, and the mileage proxy next to the source trail.
Source: Gridwise Uber 2026 pay data →Top-result comparison
Where GigVerdict has to beat the pages ranking for Uber San Francisco Pay Per Mile
The strongest search results usually win one trust signal at a time: official pay rules, a real driving test, a large driver dataset, fresh salary aggregates, or raw driver discussion. This page has to combine those signals with a city-level $19.93/hr net estimate.
Official pay docs
|
Uber official pay docs
Ranks because it is the source of truth for pay components.
Usually missing: Official pages explain how Uber pay works, but they do not answer whether per mile in San Francisco clears expenses.
GigVerdict response: Keep the official pay components visible, then convert the San Francisco baseline into $19.93/hr net after mileage and self-employment tax.
Source: Uber official pay docs →
Coverage docs
|
Uber official city directory
Wins availability intent before any earnings estimate matters.
Usually missing: Coverage pages confirm whether the platform is active, but they do not model a 276-mile week, local gas, or take-home pay.
GigVerdict response: Link users to the official availability check, then bring them back to the San Francisco earnings model and calculator.
Source: Uber official city directory →
Field test
|
NerdWallet Uber field test
Wins trust by showing a real drive instead of a generic average.
Usually missing: One field test is vivid, but it is not a city-by-city planning system and may not match this market, schedule, or vehicle.
GigVerdict response: Use field-test friction as evidence, while keeping the San Francisco page specific to $1105 gross, 276 miles, and 38 hours.
Source: NerdWallet Uber field test →
Large dataset
|
Gridwise Uber pay data
Wins by aggregating many driver records and showing platform-level direction.
Usually missing: Large app-wide datasets are strong, but they usually flatten San Francisco timing, traffic, and vehicle-cost differences.
GigVerdict response: Use large-data context as a sanity check, then expose local net hourly, per-mile, and target-hour calculations.
Source: Gridwise Uber pay data →
Expert guide
|
The Rideshare Guy Uber guide
Wins because experienced driver publishers explain tactics and pay ranges.
Usually missing: Expert guides are useful, but broad app advice often stops before a city-specific after-expenses answer.
GigVerdict response: Translate the broad tactic into a San Francisco planning page: hours, miles, gross needed, tax pressure, and related intent links.
Source: The Rideshare Guy Uber guide →
Salary aggregate
|
Indeed Uber Driver salary data
Wins freshness and volume with constantly updated salary snippets.
Usually missing: Salary aggregators mix regions, worker types, and reporting methods, and rarely separate gross pay from 1099 costs.
GigVerdict response: Show a transparent 1099 model instead: $19.93/hr net after the 2026 mileage proxy and self-employment tax.
Source: Indeed Uber Driver salary data →
Driver forum
|
Uber driver discussion
Wins because drivers search for current pain, saturation, and real shift stories.
Usually missing: Forum answers are fast and candid, but they are noisy, unstructured, and often hard to compare across cities.
GigVerdict response: Turn the driver pain points into structured checks for San Francisco: active time, dead miles, target hours, and market timing.
Source: Uber driver discussion →
Tactical app blog
|
ShiftTracker Uber driver guide
Wins with practical 2026 advice around boosts, tracking, and expenses.
Usually missing: Tactical posts help drivers operate, but they usually do not give a clean city URL for a single earnings question.
GigVerdict response: Make the page match one high-intent query, then point users into the calculator when their San Francisco routine differs.
Source: ShiftTracker Uber driver guide →
Policy report
|
Seattle Driver Union pay calculator
Wins when the user wants take-rate, labor, and fairness context.
Usually missing: Policy pages explain why driver pay can feel broken, but they are usually not a shift-level earnings planner.
GigVerdict response: Keep policy and take-rate pressure as context while answering the practical net-pay question on the page.
Source: Seattle Driver Union pay calculator →
Creator SERP
|
Uber pay creator SERP
Wins attention with screenshots, daily goals, and relatable shift narratives.
Usually missing: Videos are persuasive, but they are slow to scan and rarely expose a reusable city calculator or source trail.
GigVerdict response: Answer the creator-style money question in text: whether San Francisco can reach the target, how many hours it takes, and what miles it costs.
Source: Uber pay creator SERP →Driver field notes
What drivers check before trusting a Uber earnings number in San Francisco
These notes come from field tests, official platform docs, driver discussions, and gig-economy reports. They are not guarantees; they are the friction points a real driver would check before treating $19.93/hr net as realistic.
Field test
Miles can overwhelm a strong Uber fare day
A recent Uber field test reported about 10 active hours, 10 trips, and 305 miles. For San Francisco, the mileage load is why this page starts with $19.93/hr net instead of gross fare totals.
Source: NerdWallet Uber pay test →Online time
Drivers judge waiting time, not only booked trips
Uber's earnings tools show session summaries with online time, offers, and completed trips. That is the right mental model for comparing a city: unpaid waiting and repositioning time change the real hourly rate.
Source: Uber delivery earnings guide →Mileage floor
A low dollar-per-mile offer can erase the shift
Driver threads often use a dollar-per-mile floor before accepting work. The 2026 IRS business mileage rate is $0.725/mi, so San Francisco drivers should compare every offer against miles, not only dollars.
Source: IRS 2026 mileage rate →Market timing
Peak windows beat all-day availability
Recent driver discussions keep repeating the same pattern: good markets can work at peak windows, while summer, school breaks, slow months, and driver saturation make all-day grinding much less reliable.
Source: Driver discussion on 2026 demand →Platform spread
Customer prices can rise while driver pay barely moves
Gridwise reported customer rideshare prices up 9.6% and platform fees up 33.2%, while driver gross pay per hour rose 4.1%. That gap is why net earnings pages need cost and time assumptions.
Source: Gridwise 2026 gig mobility report →Published shift evidence
Real Uber shift signals for San Francisco
These are reviewed public field tests and driver discussions, not scraped personal data. When a source reports gross pay, hours, miles, or deliveries, GigVerdict shows those fields separately so the modeled $19.93/hr net estimate can be checked against real-world shift friction.
Field test
rideshare driving
National Uber field test
10 active hours, 10 trips, and 305 miles
Gross
Not reported
Active hr
10.0
Dash/online
Not reported
Miles
305
Reported deliveries: 10
Uber screenshots need a mileage check because a strong fare day can still put heavy depreciation on the car.
Source: NerdWallet Uber pay test →
Reddit self-report
early-morning and surge-only driving
Tennessee UberX/Lyft year report
$23,611 gross after platform fees and tolls, 18,426 miles, $38 gross/hour, $1.28/mile
Gross
$23611
Active hr
Not reported
Dash/online
Not reported
Miles
18426
The driver used a 2014 Honda Civic and only drove selected surge and early-morning windows. The post does not provide enough verified time detail for a net-hourly estimate.
Source: Tennessee UberX/Lyft gross earnings report →
Reddit self-report
4-6 peak hours per day across six apps
Uber Eats EV multi-app month
$3,400-$4,000 monthly across six apps, with $3-$9 off-peak EV charging
Gross
Not reported
Active hr
Not reported
Dash/online
Not reported
Miles
Not reported
This is a multi-app delivery report, not Uber rideshare-only data. The useful evidence is that vehicle type, charging cost, peak-window selection, and app mix materially change the result.
Source: Uber Eats multi-app EV earnings discussion →Driver report intake
Share a real Uber shift in San Francisco
Modeled earnings are useful, but actual shifts are the data moat. Submit gross pay, miles, hours, and the window you drove so future San Francisco pages can compare the model against real driver reports.
Current model
$19.93/hr
Report status
Editorial review
Use the next page by intent
Related San Francisco Uber questions
After Gas
Use this when the gross payout looks fine but fuel and mileage may erase the shift.
Active Time
Use this when app-reported active time may hide unpaid waiting and repositioning time.
Worth It
Use this when deciding whether the city is worth driving at a realistic side-hustle pace.
$100 a Day
Use this when the question is how many real hours and miles it takes to clear a $100 net day.
$1,000 a Month
Use this when planning a monthly side-income target instead of judging one shift.
Nights and Weekends
Use this when the plan is to drive around a 9-to-5 schedule instead of all-day availability.