how long does for a car to install an over-the-air software update?

Most car over-the-air software updates take about 20 to 60 minutes to install after the update has finished downloading. Smaller infotainment or navigation updates may finish in 10 to 20 minutes, while a large update involving several vehicle control modules can take an hour or more. The estimated time shown by the vehicle or manufacturer’s app is more useful than a general average because the car knows which update package it received.

Downloading is a separate stage. It may occur quietly while the vehicle is being driven or parked and can take from several minutes to hours, depending on the file size and connection. The car may then need to be parked, turned off, sufficiently charged, and left unused during the actual installation.

Quick Answer

Plan on leaving the car unavailable for at least one hour unless its screen or app gives a shorter manufacturer-specific estimate. Current manufacturer examples vary: BMW describes installation in about 20 minutes, Tesla says some updates take approximately 30 minutes and some take longer, Ford says most updates that make the vehicle non-drivable finish within 45 minutes, and Hyundai documents certain updates at about 15 minutes. Downloads may take much longer and often happen beforehand. Do not begin an update immediately before a trip, during an emergency, or anywhere the vehicle must be moved.

Typical Over-the-Air Car Update Timeline

Update stage or type	Typical planning range	Can the car usually be driven?
Waiting for the manufacturer’s rollout	Days or weeks after an update is announced	Yes
Background download	15 minutes to several hours; sometimes spread across drives	Often yes, depending on the manufacturer
Package verification and preparation	A few minutes to 30 minutes	Sometimes; it may occur in the background
Small infotainment or map installation	About 10 to 30 minutes	Infotainment may be unavailable; follow the vehicle’s warning
Typical parked, non-drivable installation	About 20 to 60 minutes	No
Large multi-module or operating-system update	About 60 to 90 minutes or longer	Usually no
Restart, validation, and feature initialization	Several minutes after the main progress bar finishes	Wait for the completion message
Failed update requiring another attempt	Another full update window or a dealer visit	Depends on the failure and manufacturer instructions

These ranges are planning estimates, not promises. A particular update may fall outside them, and the vehicle’s own instructions take priority.

What Counts as the Installation Time?

People often start timing an update when the notification first appears. Automakers may start the installation estimate later, after the file is already downloaded and the car has passed its readiness checks.

A complete OTA update can involve five separate clocks:

Rollout: The manufacturer decides when that vehicle identification number receives the release.
Download: The update package is transferred by cellular data, Wi-Fi, or a connected phone.
Preparation: The vehicle checks the package, available storage, software compatibility, battery condition, and other prerequisites.
Installation: Software is written to the target systems and activated.
Restart and validation: The affected computers restart, communicate with one another, and confirm that the new version is operating correctly.

The dashboard estimate may describe only step four. A notice saying “30 minutes” does not necessarily mean the entire process from announcement to finished vehicle takes 30 minutes.

Downloading Versus Installing

The distinction matters because the two stages affect the driver differently.

Downloading

The car receives data but may continue running its existing software. Some manufacturers allow downloads while driving. Others prefer or require a reliable cellular or Wi-Fi connection while parked.

The download can pause and resume if:

the vehicle leaves Wi-Fi range
cellular coverage weakens
the vehicle is powered down
data transfer is restricted
the manufacturer pauses the rollout
the car needs more driving or awake time

Tesla’s current owner documentation, for example, separates downloading from installation and says the vehicle can be driven while downloading, although leaving Wi-Fi coverage can interrupt the transfer. Hyundai documents certain map and multimedia downloads taking about 20 to 60 minutes depending on connection quality.

Installing

The vehicle begins replacing or activating software. During a parked installation, electronic control units may restart, displays may go dark, warning lights may appear, and remote functions may stop responding temporarily.

When the manufacturer says the car cannot be driven, that instruction is literal. The update may temporarily limit propulsion, charging, locks, windows, climate controls, safety systems, or the ability of vehicle computers to communicate.

Do not assume a nearly finished progress bar means the vehicle is ready. Wait for an explicit success message and normal vehicle startup.

Current Manufacturer Examples

Manufacturer estimates illustrate why one answer cannot fit every vehicle.

Manufacturer example	Published installation guidance	Important condition
BMW Remote Software Upgrade	About 20 minutes after download	Vehicle parked and unavailable during installation
Tesla vehicle software	Some updates approximately 30 minutes; some longer	Vehicle in Park and cannot be driven
Ford software updates	Most non-drivable updates within 45 minutes or less; some longer	Some updates install while driving; others require parked ignition-off time
Hyundai OTA map and multimedia update	About 15 minutes for the installation in a published example	Navigation system unavailable during installation
Hyundai Recall 293 OTA example	Average installation time about 15 minutes	Vehicle cannot be operated during the update
GM software updates	Time varies by component and update contents	Vehicle notice supplies the installation estimate

These figures do not mean every BMW, Tesla, Ford, Hyundai, or GM vehicle will match that duration. Model year, hardware, software architecture, market, installed version, update contents, and vehicle condition all matter.

Why a Car Update Can Take Longer Than a Phone Update

A modern car is not one computer. It is a network of electronic control units, sensors, gateways, displays, communication modules, and safety-related systems supplied by multiple manufacturers.

An OTA package may need to update or coordinate:

the central infotainment computer
instrument displays
navigation and map databases
battery-management software
charging controls
powertrain controllers
climate systems
body-control modules
camera, radar, or driver-assistance processors
telematics and cellular modules
cybersecurity components
mobile-app communication services

Some updates touch only one area. Others must install components in a particular order so that compatible versions remain available throughout the process.

The vehicle may also perform extensive checks before it activates the software. A failed phone update is inconvenient; an improperly updated braking, propulsion, or battery-control module can create a safety issue. Automotive update systems are designed around cautious validation, power stability, and recovery behavior.

What the Car Is Doing During the Update

The exact design is proprietary and varies, but a modern OTA process may include the following work.

Confirming Vehicle Identity and Compatibility

The system checks that the package is intended for the correct model, hardware configuration, region, and existing software level. Two vehicles that look identical can have different modules or production revisions.

Authenticating the Update

The vehicle verifies that the package came from an authorized source and was not altered. NHTSA’s vehicle cybersecurity guidance emphasizes protecting connected vehicles and software systems against cybersecurity risks.

Checking Preconditions

The car may confirm that it is parked, turned off, not charging, not in an emergency mode, and adequately powered. It may check the 12-volt electrical system as well as the high-voltage battery in an electric vehicle.

Staging the New Software

Some systems write an update to inactive storage while the current system continues running. Android’s A/B update design, which can be used as part of an automotive platform, maintains two system slots so a prepared version can be activated at reboot while the prior version remains available for recovery.

Not every vehicle or module uses A/B partitions. Some control units must be flashed directly and remain unavailable during that work.

Updating Several Modules

The car’s central update manager may pass software to individual controllers. Each module can have its own erase, write, verify, restart, and reporting sequence. Sequential work adds time even if each individual file is small.

Rebooting and Validating

The system activates the new version, restarts affected components, and confirms that they can communicate. A successful download alone does not prove a successful installation.

What Determines How Long the Update Takes?

Update Size

A small configuration correction generally takes less time than a complete infotainment operating system, map database, or multi-controller update. File size affects downloading most directly, but more code can also require more writing and verification.

Number of Modules

Updating one display computer is simpler than coordinating battery, charging, body, connectivity, and driver-assistance modules. The total may be governed by the slowest controller or a required sequence.

Current Software Version

A vehicle only one release behind may receive an incremental package. A vehicle that has missed several releases may need a larger package, prerequisite update, repeated installation, or dealer assistance.

Automakers do not all permit users to jump freely between versions, and some releases are assigned based on a particular starting version.

Vehicle Architecture

Newer centralized or zone-based electrical architectures may handle updates differently from older vehicles with many independently supplied control units. Hardware storage speed, processor performance, network bandwidth, and recovery design all affect the installation.

Wi-Fi or Cellular Quality

Connection speed usually affects the download rather than the parked installation. A weak connection can make the overall experience look slow because the car is not yet ready to install.

Battery and Electrical Condition

Control modules need stable voltage while software is being written. A weak 12-volt battery can prevent an update from starting or cause it to fail. An electric vehicle may also require a minimum high-voltage state of charge.

Ford’s current prerequisites for some non-drivable updates are especially detailed: the vehicle may need to be parked, off, closed, not charging, and sufficiently charged. The exact requirements differ by vehicle and update.

Temperature and Vehicle State

Some manufacturers require the engine or other components to be cool, the vehicle to be on level ground, the parking brake engaged, or certain features disabled. Extreme temperatures can also affect battery condition and system readiness.

Post-Installation Initialization

Navigation indexes, connected services, driver profiles, cameras, and assistance features may need additional startup time. A main progress indicator can reach 100 percent before every convenience feature is fully ready.

Why the Update Is Available to Someone Else First

An announced update is not necessarily available to every eligible vehicle on the same day.

Automakers commonly use staged rollouts. A release may begin with a small fleet, expand to additional hardware combinations, and pause if monitoring reveals a problem. Deployment can depend on:

model and model year
country or regulatory market
hardware revision
installed software version
factory configuration
connectivity status
fleet or employee testing groups
recall population
release channel or update preference

Tesla’s owner documentation says delivery depends on factors unique to each release and vehicle. Selecting an earlier release preference does not guarantee immediate delivery.

Waiting a week for the update to be offered is not a week-long installation. It is rollout timing. Owners should avoid comparing version numbers without confirming that the other vehicle has the same model, hardware, region, and update path.

What Conditions Must Be Met Before Installation?

The car’s screen or app should list the controlling conditions, but common requirements include:

vehicle safely parked
transmission in Park
parking brake applied
ignition off
sufficient 12-volt battery condition
sufficient traction-battery charge for an EV
doors, hood, and trunk closed
headlights and hazard flashers off
no active alarm or emergency call
no diagnostic equipment connected
no charging session in progress
no climate, pet, camping, or utility mode operating
reliable connectivity for any remaining download
enough time before the vehicle is needed

These are not arbitrary inconveniences. They reduce the chance that a power interruption, user command, or active vehicle function conflicts with module programming.

Ford says some scheduled updates will not start if the vehicle is not properly parked and shut down or if doors are open. BMW advises a safely parked vehicle, parking brake, adequate battery charge, headlights off, and a relatively cool engine. Tesla prevents installation during certain climate-retention modes.

Always follow the instructions for the actual vehicle. Do not try to imitate another brand’s readiness checklist.

Can You Drive During an OTA Update?

Sometimes during the download, but generally not during a non-drivable installation.

Ford says many updates can download and install seamlessly while the vehicle is driven, while updates that affect vehicle availability require parked ignition-off installation. Tesla permits driving during download but states that the vehicle cannot be driven during installation. BMW also says the vehicle cannot be used during its Remote Software Upgrade installation.

The notification should identify whether the update is drivable or non-drivable. When the message says the vehicle will be unavailable:

do not start the update in a traffic lane or charging queue
do not begin immediately before school pickup, work, a medical appointment, or a trip
do not remain dependent on electronic doors without reviewing the owner’s instructions
do not attempt to start, shift, charge, or move the vehicle
do not disconnect the 12-volt battery

The fact that an app still communicates with the car does not mean the car is safe to drive.

Can You Stay Inside the Car During Installation?

Manufacturer guidance varies, and leaving the vehicle is usually the simpler choice when permitted.

During an update:

displays may turn off or restart
locks and windows may be unavailable
climate controls may stop
alarms or warning messages may appear
remote commands may not work
charging may pause
interior lights and accessories can consume 12-volt power

Read the update notice before confirming. Secure belongings, make sure people and animals are out when the car may become inaccessible, and take needed medication, keys, phones, and mobility equipment with you.

Never use a parked update as a time to leave a child, dependent adult, or animal in the vehicle. Climate and door functions may be disabled.

Does the Car Need to Be Plugged In?

Not necessarily. Some electric vehicles pause charging during installation, while others may have different requirements. A gasoline vehicle still relies on its 12-volt battery and may need recent driving or adequate charge before the update begins.

Tesla states that charging stops during installation and resumes afterward. Ford says certain electric vehicles cannot be charging during a non-drivable update and specifies a high-voltage charge requirement for some updates.

Do not assume plugging in is always safer. Follow the vehicle’s prompt. If the installation refuses to start, the app or screen may identify charging, battery state, or another unmet prerequisite.

Does Wi-Fi Make Installation Faster?

Wi-Fi can make the download faster and more reliable, especially for a large package. It may not materially change how fast control modules write and verify the software after the download is complete.

For the best chance of a smooth download:

park where the vehicle receives a strong, stable signal
use a trusted network
keep automatic updates enabled if desired
avoid moving out of range before the package finishes
confirm that the car, not only the phone, is connected
allow the vehicle time to remain awake or complete background transfer

A full Wi-Fi icon does not guarantee high speed. Distance, walls, interference, network congestion, internet service, and the vehicle’s own radio can limit throughput.

How to Prepare Before Starting the Update

Read the Entire Notice

Look for the estimated time, whether the car will be drivable, battery requirements, charging restrictions, and any special safety instruction. Release notes may also explain a changed control or feature.

Choose a Safe Location

Park somewhere the vehicle can remain longer than the estimate without blocking another car, garage door, charger, roadway, or work area. If a recall notice says “do not drive” or “park outside,” follow that instruction exactly.

Add a Time Buffer

If the display says 30 minutes, allow at least an hour before the car is needed. A delayed start, post-installation restart, or error can consume the buffer.

Check Battery and Vehicle Conditions

Address any readiness message rather than repeatedly pressing Install. Close openings, turn off prohibited modes, stop charging if directed, and ensure adequate battery charge.

Remove People, Animals, and Needed Items

Take keys, phones, documents, medications, child seats or mobility items that may be needed. Some vehicles restrict remote unlocking or ordinary entry during certain installations.

Keep Another Transportation Option for Critical Commitments

Do not schedule a major update as the only vehicle is about to be needed for an airport trip, urgent appointment, evacuation, or work shift.

What Not to Do During Installation

Do not try to drive the vehicle.
Do not disconnect or jump the battery unless the manufacturer directs it.
Do not open service panels or connect diagnostic tools.
Do not repeatedly press controls because the screen is dark.
Do not remove a USB device if the update instructions require it.
Do not force-restart the infotainment system unless official support instructs you.
Do not assume the process failed merely because displays reboot.
Do not attempt an unofficial downgrade or software modification.

Vehicle functions can behave unusually during programming. The owner’s manual and update screen are the correct sources for that vehicle.

Why an Update May Not Start

The most common explanation is that a prerequisite has not been met.

Possible causes include:

download not complete
weak connectivity
insufficient 12-volt battery condition
low EV traction-battery charge
vehicle not in Park
ignition still on
door, hood, or trunk open
charging in progress
lights, hazards, climate, alarm, or emergency services active
engine or components too warm
another update or diagnostic operation pending
unsupported starting software version
update rollout paused
insufficient storage
server or app problem

Read the exact message. A generic “not updated” notice may have more detail in the vehicle’s software menu or companion app.

What If the Update Appears Stuck?

Progress indicators are not always linear. A module can spend a long time verifying or writing data and then advance rapidly. A dark display or temporary loss of app communication can also be normal.

Take these steps:

Note when the installation actually began.
Compare the elapsed time with the vehicle’s displayed estimate, not only a general internet estimate.
Leave the car undisturbed while the official installation window is still plausible.
Check the manufacturer’s app for a completion or failure message.
Follow the owner’s manual instructions for an unsuccessful update.
Contact the manufacturer or authorized dealer if the process exceeds the guidance, reports failure, or leaves the vehicle unusable.

Do not force a power interruption just because the progress bar pauses. If there is smoke, fire, an unusual burning odor, or another immediate physical hazard, move away, contact emergency services, and follow the manufacturer’s emergency guidance.

What Happens If an Update Fails?

The outcome depends on the vehicle architecture and failure stage.

Possible results include:

the car continues using the previous software
the update retries automatically later
the user is asked to reschedule
one feature remains temporarily unavailable
the vehicle downloads a replacement package
remote support performs diagnosis
a dealer completes recovery or programming

Systems with an inactive software slot may be able to return to the earlier working version when validation fails. Other control modules may require service tools. A vehicle being able to start does not prove that every module updated successfully.

Record the displayed error and version information before clearing notifications. Contact official support rather than relying on an unofficial sequence of button presses from a different model year.

Are OTA Updates the Same as Recalls?

No. An OTA update is a delivery method. A recall is a formal safety action involving a defect or noncompliance.

An automaker can use an OTA software update as the remedy for a safety recall when the defect can be corrected electronically. Hyundai has published recall examples using OTA installation, and NHTSA has urged owners of certain vehicles to complete urgent over-the-air recall remedies.

Owners should still:

read the recall notice
confirm whether their specific VIN is affected
follow interim warnings such as “do not drive” or “park outside”
verify that the remedy was completed
contact the dealer if OTA installation is unavailable or unsuccessful

NHTSA advises owners to check open recalls using the VIN or license-plate lookup and to complete safety remedies promptly. A feature-update notification is not a substitute for checking recalls.

Why OTA Update Security Matters

Vehicle updates may affect systems far beyond entertainment. The update chain must protect authenticity, integrity, compatibility, and recovery.

Security controls may include:

encrypted communication
signed update packages
certificate and source verification
secure boot or verified boot
hardware and version compatibility checks
rollback protection
update logs and audit records
separation of infotainment from safety-related systems
recovery images or alternate partitions

NHTSA’s cybersecurity best practices stress that connected-vehicle cybersecurity should be treated as a safety priority. ISO 24089 establishes requirements and recommendations for road-vehicle software-update engineering across organizations, projects, vehicles, systems, electronic control units, infrastructure, and update packages.

These checks add time, but skipping them would create unacceptable risk.

Can You Roll Back to the Previous Version?

Usually not through an ordinary owner control. Some update systems retain an older slot for automatic failure recovery, but that does not mean the driver can choose any past version.

Automakers may block downgrades because an older release:

contains a safety or cybersecurity defect
is incompatible with updated modules
no longer matches server services
changes regulated functionality
could corrupt data created by the newer version

Tesla’s owner documentation states that returning to a previous software version is not available. Other manufacturers have their own policies. If an update creates a problem, document the symptoms and contact official service rather than attempting an unsupported rollback.

How to Know the Update Is Finished

Look for more than the disappearance of a progress bar.

A completed update may produce:

an explicit successful-installation message
normal startup of displays and controls
a new software version in Settings
release notes
an app notification
restored charging or remote-control functions
removal of the update alert
a completed recall status after the manufacturer processes the repair record

The last item may not update instantly in a recall database. Manufacturer reporting and database processing can take additional time even though the vehicle software is already installed.

After completion, read the release notes before driving. Controls, driver-assistance behavior, charging settings, privacy choices, or menu locations may have changed.

What to Check Before the First Drive After an Update

Take a minute to confirm that the vehicle has returned to an ordinary operating state. Check that the instrument panel starts normally, no unexpected warning remains, the transmission can be selected as usual, and the update menu reports success. Review any release notes before relying on a changed feature.

It is also sensible to verify settings that can affect the next trip:

driver-assistance preferences and warning sensitivity
charging limit, departure time, and home-charging schedule
climate preconditioning and remote-start settings
phone pairing, navigation favorites, and driver profiles
privacy, data-sharing, camera, and location choices
digital keys and authorized drivers

A changed menu location is not necessarily a malfunction. However, a persistent safety warning, loss of a required vehicle function, or repeated update-failure message deserves official manufacturer or dealer support before normal driving. Avoid experimenting with assistance features in traffic; learn any changed control in a safe, stationary setting first.

Frequently Asked Questions

How long should I plan for a car OTA update?

Allow at least one hour unless the vehicle provides a different estimate. Many published manufacturer examples fall between about 15 and 45 minutes after download, but large or multi-module updates may take longer.

Is the download included in the installation estimate?

Often it is not. Automakers commonly download the package in the background and display the installation estimate after the file is ready. Check the wording on the vehicle’s screen or app.

Can I drive while my car downloads an update?

Some manufacturers allow background downloading while driving. Connectivity loss may pause the transfer. Follow the vehicle’s instructions because download behavior varies by brand, model, and update.

Can I drive while the software installs?

Not when the update is labeled non-drivable or requires parked installation. Important vehicle systems may be temporarily unavailable. Wait for the explicit completion message before using the car.

Will the update continue if Wi-Fi disconnects?

A completed download can often install without continued Wi-Fi, but an incomplete transfer may pause. Some vehicles also use cellular connectivity. The update screen should show whether the package is downloaded and ready.

Does an electric car need to be charging during an update?

Not necessarily. Some vehicles pause charging or require that charging be stopped during installation. They may also require a minimum battery level. Follow the vehicle-specific prompt rather than assuming it should remain plugged in.

Can a weak 12-volt battery delay the update?

Yes. Electronic control units need stable voltage during programming. A car may postpone installation if its battery-management system determines that the electrical condition is inadequate.

Why did my scheduled update not begin?

The car may not be in Park, fully shut down, sufficiently charged, or in the required physical state. Open doors, active lights, charging, climate modes, alarms, emergency calls, weak connectivity, or an incomplete download can also block installation.

Is it normal for the screen to go black during an update?

It can be normal for displays and electronic modules to restart. Do not press controls or force a reboot unless the owner’s manual or official support specifically directs you to do so.

What should I do if the progress bar does not move?

Allow the full manufacturer-provided estimate plus a reasonable buffer. Check the app for status and follow the official failure instructions. Contact the manufacturer or dealer if the update exceeds the guidance or leaves the vehicle unusable.

Can an OTA update fix a safety recall?

Yes, when the safety defect can be corrected with software and the manufacturer offers OTA as the approved remedy. Follow the recall notice and verify the remedy for the specific VIN.

Will an OTA update reset my personal settings?

It may change, reset, or add some settings, but behavior depends on the release. Review driver profiles, charging schedules, privacy controls, assistance settings, paired phones, and release notes afterward.

Can I cancel a car software update after it starts?

Often not during a non-drivable installation. Interrupting module programming can cause a failure. Reschedule before confirming when the vehicle permits it, then leave the process undisturbed once installation begins.

Why does another identical car already have the update?

Rollouts are staged and can depend on region, hardware revision, installed version, configuration, and release group. Two vehicles with the same model name may not have the same update eligibility or schedule.

Quick Summary

Most over-the-air vehicle software installations take about 20 to 60 minutes after the package is downloaded. Published examples include about 20 minutes for BMW, approximately 30 minutes for some Tesla updates, 45 minutes or less for most Ford non-drivable updates, and about 15 minutes for certain Hyundai installations. The vehicle’s displayed estimate is the best guide for the specific release.

Downloading, rollout waiting, preparation, installation, and validation are separate stages. A weak connection can stretch the download over hours or several drives without increasing the actual module-programming time. Large updates that affect several controllers can take more than an hour.

Before confirming a parked update, read the notice, choose a safe location, allow a generous buffer, satisfy all battery and vehicle-state requirements, and remove people, animals, and needed belongings. Do not attempt to drive, charge, disconnect power, or force-restart the car while a non-drivable update is running. If a safety recall is involved, follow the recall instructions and confirm the remedy for the vehicle’s VIN.

Sources & References

Editorial Review

Reviewed by Claire Bennett, Managing Editor

Last reviewed: August 2026

Quick Answer Guide publishes practical, research-based answers to common questions about money, technology, health, travel, home improvement, and everyday life. Content is reviewed using official government resources, educational institutions, industry publications, and other authoritative sources when appropriate. Articles are updated periodically to improve accuracy and usefulness.

How Long Does It Take for a Car to Install an Over-the-Air Software Update?