Embedr is a desktop app. Your project files live on your machine. Some services, such as sign-in, model access, datasheet processing, model catalog sync, and updates, use the internet.
Install the desktop app
Download Embedr from the website download page for your operating system.
macOS
- Download the
.dmg. - Open it and drag Embedr into Applications.
- Launch Embedr from Applications.
- If macOS blocks the first launch, open System Settings and allow the app, or right-click the app and choose Open.
Use a USB data cable when working with boards. Many "charging" cables power a board but do not expose a serial port.
Windows
- Download the installer.
- Run it and follow the setup prompts.
- Launch Embedr from the Start menu or desktop shortcut.
- Install board-specific USB drivers if your device does not appear in the Device dropdown.
Common drivers are CH340 or CH341 for many Arduino-compatible boards, CP210x for many ESP32 boards, and FTDI for older USB-to-serial adapters.
Linux
Use the Linux build provided for your distribution format. You may need to add your user to the serial device group, often dialout, before uploads or serial monitor access work.
First launch
On first launch, Embedr shows the welcome and account flow. The app stores local preferences using electron-store, and it remembers recent projects, selected target, panel sizes, font sizes, chat thread state, and other local UI choices.
The managed firmware runtime is bundled with packaged builds. In development builds, Setup & Diagnostics can show whether the runtime resolved correctly.
Sign in
You can sign in with email and password or with Google. Email sign-up requires a name, email, password, and acceptance of the terms. If the account needs verification, Embedr will show a verification state and let you resend the verification email.
Password reset is available from the sign-in screen.
Why sign-in exists
Sign-in is used for services that cannot safely run fully local:
- model access for Embedr Agent,
- usage and subscription status,
- secure authenticated calls to cloud functions,
- datasheet processing,
- billing and account management.
Your project files are not moved into the app account by default. A firmware file remains where you created or opened it.
Billing and upgrades
Open Settings from the Home screen and choose Billing & Upgrades. That opens the web billing flow associated with your signed-in account.
Billing state is read from your account subscription document. If subscription state cannot be loaded, the app falls back to a safe default and may show limited access until it can refresh.
Deep links
Embedr registers an embedr:// protocol. The website can use it to pass sign-in results back to the desktop app. A deep link is not a project file. It is a command-style URL handled by the operating system and routed to Embedr.
If a sign-in deep link does not return to the app:
- make sure Embedr has been installed, not only downloaded,
- launch the app once from the operating system,
- retry the browser flow,
- reinstall the app if the protocol registration is stale.
What works offline
Offline behavior depends on what is already installed and cached.
Usually works offline:
- opening local projects,
- editing files,
- viewing project history,
- compiling with already installed PlatformIO platforms and libraries,
- serial monitor,
- terminal commands.
Requires internet:
- first-time sign-in,
- agent responses,
- model catalog updates,
- library or platform downloads not already cached,
- datasheet PDF processing,
- update checks,
- registry sync beyond bundled board presets.
Local storage locations
Project files live wherever you created or opened the project. App preferences live in the app data directory for your operating system. Datasheet index metadata is stored under Embedr's app data directory, while processed datasheet markdown and images are stored inside the project.
That split matters. Back up project folders like normal source repositories. Back up app settings separately only if you care about UI preferences and local app state.