Knowledge Base
🇨🇦 EN

Which browser should I use with MakeCode and the Forward Education Learning Platform?

The short answer

Use Google Chrome or Microsoft Edge, and keep them up to date. Both MakeCode and the Forward Education Learning Platform work best in these two browsers, and they're the ones we test against.

If your class is on Chromebooks, you're already set. ChromeOS uses Chrome.

Why Chrome and Edge?

The main reason is a browser feature called WebUSB. WebUSB lets a web page talk directly to a device plugged into your computer's USB port, and in this case, your micro:bit.

With WebUSB working, you get:

  • One-click downloads. After you pair your micro:bit once, pressing Download in MakeCode sends the program straight to the board. No dragging a .hex file onto the MICROBIT drive every time you make a change (micro:bit support).
  • Live data from the board. MakeCode can show console output from your micro:bit, which is how students see live sensor readings from Climate Action Kit modules instead of just guessing.
  • Fewer mid-class hiccups. Faster flashing means less waiting and fewer "it didn't save" moments when 25 students are downloading at once.

Google Chrome and Microsoft Edge are currently the browsers that fully support flashing directly from the browser this way.

Minimum versions

Microsoft's MakeCode documentation lists these minimums for WebUSB (MakeCode WebUSB page):

  • Google Chrome version 79 or newer
  • Microsoft Edge version 79 or newer
  • If you're using an older micro:bit V1 board, its firmware needs to be version 0249 or above

In practice, the advice from the micro:bit Foundation is simply to run the most recent version of your browser. That matters in schools, where automatic browser updates are sometimes delayed or disabled by IT for security reasons.  A device that hasn't updated in a year or two can be well behind.

How to check your browser version

  1. In Chrome, open the menu (⋮) in the top-right corner, then choose Help → About Google Chrome.
  2. In Edge, open the menu (…) in the top-right corner, then choose Help and feedback → About Microsoft Edge.
  3. The page shows your version number and will update the browser automatically if an update is available.
  4. Restart the browser when prompted, then reload MakeCode.

If the update is blocked or greyed out, your device is managed by your school and your IT team will need to push the update.

What about Safari, Firefox and iPads?

Safari does not support WebUSB, so it can't connect to a micro:bit. The same is true of other non-Chromium browsers such as Firefox. You can still browse the Learning Platform in them, but coding and downloading to the board won't work reliably.

iPads currently have trouble connecting consistently to the micro:bit, which is essential for Climate Action Kit projects.

If you're stuck with another browser today

You can still get code onto a micro:bit without WebUSB:

  1. Write your program in MakeCode as usual.
  2. Press Download. The browser saves a .hex file to your Downloads folder.
  3. Plug the micro:bit into the computer with a USB cable. It appears as a drive called MICROBIT.
  4. Drag the .hex file onto the MICROBIT drive. The yellow light on the back of the micro:bit flashes while it copies.
  5. Repeat steps 2–4 every time you change the code.

It works, but it's several extra steps per change, which adds up quickly across a class period. Switching to Chrome or Edge is worth the five minutes.

Classroom notes

  • Pairing is per browser and per computer. If students switch browsers, switch laptops, or use a fresh profile, they'll need to pair their micro:bit again in MakeCode. Budget a couple of minutes for this at the start of a lesson on new devices.
  • Pick one browser for the whole class. Mixed browsers make troubleshooting much harder when you're helping several groups at once.
  • To unpair a micro:bit, click the lock icon in the browser's address bar and clear the listed micro:bit device, then reload the MakeCode page.

Lock icon in the browser address bar used to unpair a micro:bit

Still not connecting?

If you're on an up-to-date Chrome or Edge and the micro:bit still won't connect, the browser usually isn't the problem.  Check the USB cable (some cables are charge-only), try a different USB port, and fully power down the micro:bit by unplugging both the battery pack and the USB cable before reconnecting.

For school-managed networks, also check with your IT team that the required Forward Education and MakeCode domains are allowed through the web filter. See the existing article on what domains your school district needs to whitelist.

Still stuck? Reach out to our support team and let us know the browser, browser version, and device type you're using. That's the fastest path to a fix.