Start Here with FORScan

Start Here with FORScan

This is the getting-started hub on forscan.com. Forscan.com is an independent guide — not the FORScan developers, and not a place that hosts the software or sells licenses. Download FORScan only from forscan.org. If a page offers a “FORScan download” from anywhere else, a cracked Extended license, or an installer bundled with extras, close it.

Start with the right adapter, make sure your setup is stable, and understand the change before you write anything to your vehicle. Work through this page once, in order. The goal is a first successful connection, not a first write.

What FORScan is

FORScan is a diagnostic and module configuration application for Ford, Lincoln, Mercury and Mazda vehicles. It reads and clears fault codes across every module the vehicle exposes — not just the engine — shows live data, runs service procedures, and lets you view and edit As-Built so you can enable factory features that were switched off when the car left the plant. That last part is why people install it, and why a careless session can cause real problems.

This site is the practical part: install, adapter, which changes are worth doing, and how to get out of trouble when a scan will not connect.

Windows vs Lite

Windows is the full version of FORScan. Use it to read and clear error codes, see live data, run tests, or change vehicle settings such as lights, tyre size, or comfort options. FORScan Lite on Android or iPhone is convenient for phone-based diagnostics and supported tests. Lite cannot change vehicle settings. If configuration is even a maybe later, start on a Windows laptop. A mobile-only kit will not grow into a coding setup.

Pick an adapter before you install

FORScan is only as reliable as the interface between your laptop and the OBD-II port. Choose the adapter for the job you actually have. The live comparison is Best FORScan Adapters for 2026. Still matching a phone versus a laptop? Use which FORScan adapter do I need?

  • Windows laptop, especially changing settings: OBDLink EX (USB).
  • iPhone, iPad, or wireless diagnostics: OBDLink MX+ (Bluetooth).
  • Budget Windows route: OHP ELM327 (FORScan edition, USB or Wi-Fi) for codes, live data and occasional coding — not as if it were full-function.

A generic ELM327 is not in the 100% compatible set. Only OBDLink EX / MX+ and the small set FORScan actually recommends count as 100% compatible. The OHP ELM327 is still a sensible budget option, with that limit stated. Many Fords built before roughly 2016 need HS-CAN and MS-CAN. The MX+ reads both HS-CAN and MS-CAN and switches between them automatically, so there is no toggle to flip on pre-2016 vehicles.

Paid Extended vs the trial

Windows FORScan is fully functional only if both are true: a paid Extended license, and a fully compatible adapter. The free two-month trial Extended license might not be 100% functional — treat it as a look at what Extended does, not the complete tool.

Standard still does a great deal: full-system fault codes, live data, freeze frames, basic tests and reports. For a warning light, that is often enough. Extended unlocks service and configuration functions, including As-Built editing. If you need that work fully available, buy paid Extended. Request licenses from your account on forscan.org only.

Install FORScan on Windows

Follow how to install FORScan on Windows. That guide covers the download from forscan.org, adapter drivers and COM port setup, and the first successful connection. You do not need the vehicle connected just to install the program. Confirm that Windows sees the adapter before you open FORScan. If FORScan still says adapter not found or cannot connect, use the COM port fix guide.

First connection

Plug the adapter into the OBD-II port, usually below the dashboard near the driver’s seat. Turn the ignition on as instructed by your vehicle and FORScan; do not start the engine unless a procedure calls for it. Open FORScan, select the correct connection type if it asks, and let it read the vehicle and modules before attempting any change. Start by reading codes and live data. A first session that only looks is a successful session.

Before you write anything

  • Back up As-Built first. Read and save the full As-Built for every module you intend to touch, and keep the file somewhere you can find it. Write down the original values of any line you edit, too.
  • Watch battery voltage. Aim to stay above about 12.5 V. Use a battery support unit or charger for longer sessions rather than idling the engine, and abandon a write if voltage starts sagging.
  • One change at a time. Apply a single edit, exit, cycle the ignition, and confirm the behaviour before moving on.
  • Use a stable connection. Never write over a flaky Bluetooth link, and do not unplug the adapter or close the laptop lid mid-write. Wired Windows is the usual starting point for coding.
  • Stop on “adapter not compatible.” That message is a signal to check the setup. It does not always mean the adapter is unusable, but it should not be ignored — especially before configuration changes. Read adapter not compatible, don’t panic before you continue.

FAQ

What do I need to get started with FORScan?

A Windows laptop, FORScan for Windows from forscan.org, and a compatible OBD-II adapter. Add a paid Extended license only if you want to change vehicle settings or program modules.

Can I use FORScan on a Mac?

Not natively. forscan.org says Mac OS and Linux versions are planned but not coming soon, so the full program needs a Windows PC.

Can I change vehicle settings from my phone?

No. FORScan Lite for iPhone and Android is built for diagnostics, live data and some tests, but it has no configuration or programming functions. Coding is a Windows job.

Do I need to back up before changing settings?

Yes. Save the module’s original As-Built values before any change, keep the battery voltage stable, and use a reliable connection so you can restore the original settings if something goes wrong.

Where to go next

If something is not working, start with compatibility, connection, and adapter troubleshooting rather than retrying a write. Read the whole guide for the change you plan to make; do not treat a setting name as a complete instruction.