Skip to content



Download Conveyor

Installing on macOS

After dragging to your Applications folder open the Conveyor app and click "Add to path" in the UI.

Create a sample project

  • Run the following commands.
conveyor generate electron
cd my-project
npm install

Create the unpackaged app

  • Use the run command to create the packaged form of the app and run it.
conveyor run
  • Get the app into the output directory.
conveyor make windows-app

One of the following for Intel/Apple Silicon Macs respectively:

conveyor -Kapp.machines=mac.amd64 make mac-app
conveyor -Kapp.machines=mac.aarch64 make mac-app
conveyor make linux-app
  • Open the output directory and run the app you find inside.

The unpackaged app won't update. We'll fix that now by creating a download/update site.

Serve the download site

conveyor make site
cd output
npx serve .

It's self-signed, so you'll need to follow the instructions for how to install it. We'll fix that later.

Release an update

In another terminal tab:

  • Edit package.json and change the version field to 2.0.
  • Run npm install to update package-lock.json.
  • Run conveyor make site to regenerate the download site.

Run the program you installed in the previous step. You should see a window appear with a progress bar, the update be applied and the app should then start, all without any user interaction.

This happens because the sample conveyor.conf file is using the app.updates = aggressive key. Learn more about update modes.

Run the program you installed in the previous step. You should see a window appear with a progress bar, the update be applied and the app should then start, all without any user interaction.

This happens because the sample conveyor.conf file is using the app.updates = aggressive key. Learn more about update modes.

If on Debian derived distributions: Run apt-get update; apt-get upgrade to get the newest version of your app. Otherwise, there is no automatic update supported right now, sorry.

Read the config

It looks like this:

include required("/stdlib/electron/electron.conf")

// Import metadata from your package.json file and 
// which version of Electron to use.
package-json {
  include required("package-lock.json")

app {
  display-name = "My Project"
  rdns-name =
  site.base-url = "localhost:5000"
  updates = aggressive
  icons = icons/icon.svg


The conveyor.conf syntax is a superset of JSON designed for humans writing config files. You can write raw JSON if you're ever unsure about syntax. = 123 is equivalent to app { foo { bar = 123 } }.

Setting the Electron version

An Electron app must set the app.electron.version key. The /stdlib/electron/electron.conf file imported in the snippet above contains a line like this:

app.electron.version = ${?package-json.packages.node_modules/electron.version}

which will import it from the package-lock.json file.

Change the icon

The current icon is the Electron logo, which isn't a great choice for your app. Conveyor can draw icons for you.

  • Delete the line that says icons = icons/icon.svg.
  • Run conveyor make rendered-icons
  • Look in the output directory to find your new icons.

Basic, but functional.

  • Set the app.icons key to this:
    app {
      icons {
         label = XY
         gradient = blue
  • Rerun conveyor make rendered-icons and look at the results again.


Icon generation is meant for quick prototypes, internal tools, student projects and other cases where it's just not worth drawing a pretty icon for your app.

Learn more about icons

Upload a real update site

Your installs will look for updates at the location set by

  • Set the app.license key to the name of your software license e.g. Apache 2, GPL-3 etc. Use SPDX codes if you aren't sure what to put here.
  • Upload your project source code to GitHub. In your config set this key: app.vcs-url = "".
  • Create a Fine Grained Personal Access Token with Read and Write access to your repository Contents.
  • Set the key to the value of the token created above.
  • (optional) Set the key to gh-pages.
  • Run conveyor make copied-site.

Your installs will update to whatever the latest release is.

You don't have to use GitHub. If you want to upload your site elsewhere make sure app.vcs-url is set to the URL of your source repository and set to the URL where the generated site will be uploaded to.

When your key is set to localhost or a domain that ends in .local Conveyor is in testing mode and you can use it for free. Once you set to a real website you will be asked to pay and granted three license keys. Each key can be used with one site URL. If you want different update channels (e.g. beta, testing) then you'll need to different site URLs and one key for each.

  • Pick a site URL and set to point to it, e.g. app { site.base-url = "" }
  • Set the conveyor.billing-email key to the email address we can use to contact you for billing purposes.
  • Run conveyor make site.
  • You'll be asked to visit a payment URL where you can enter credit card data, and the conveyor.license-key key will be set to a short random code. This key is linked to your chosen download site URL.
  • Pay us (boo/hooray!) and rerun conveyor make site. You should now get files that can be uploaded to your chosen site URL.

To release an update you just re-upload/overwrite the files at the site URL.

Automatic site uploads

If you aren't using GitHub Releases and your download site is accessible using SSH, Conveyor can upload the results for you. Set to something like "s" i.e. the URL you'd use with sftp. Then use conveyor make copied-site to build the site and upload it all in one step. Also, remember the deploy workflow created in GitHub actions? You can run it to start a build/package/release sequence automatically.

Learn more about download sites


Your users must follow annoying instructions to install the app. That's because it's being self-signed, not signed by a recognized certificate authority. Let's fix that.

When you ran your first command Conveyor announced it had generated a "root key" and that you should back it up. It also generated two .csr files and printed the paths to them.

The root key is stored in your defaults.conf file and looks like this:

app.signing-key = "little peace follow cave drive pluck pony rebel grant barrel mammal skate devote skate amateur abandon shaft farm relax cousin few initial olive catch/2023-01-27T16:28:23Z"


  • Make a backup of your root key.

You must always back up your root key, even if you will later import signing keys you already have. The root key is also used for signing Mac update feeds, Linux packages and apt repositories.

It's represented as words so you can write it down with pen and paper for quick and safe offline backups. Remember to include the generation date!

All the different keys you need can be deterministically derived from this one root key.

How to buy new certificates

A certificate request file (CSR) can be uploaded to a certificate authority like Apple, DigiCert or to get back a certificate. The certificate links your public key to a verified personal or corporate identity and is included inside the app binaries on Windows and macOS along with the signatures.

  • Log in using an Apple ID to the Apple developer programme. Joining will require a credit card payment.
  • Request a "Developer ID Application" certificate using the Apple Developer console. You can do this with any web browser and operating system, but you must be the account holder.
  • Upload the apple.csr file that was created next to your defaults.conf file when you created your root key above.

You'll get a .cer file back immediately. There is no review or approval process because the verification is linked to your credit card details.

  • Pick a certificate authority that sells Authenticode certificates. DigiCert is a good choice. Please refer to this FAQ section for more information on the difference between normal and EV certificates.
  • Upload the windows.csr file that was created next to your defaults.conf when you created a root key above. You will need to verify your identity with the CA.
  • Download the certificate in a format of your choice. Conveyor understands several but PEM works well.
  • Place your certificate files next to your defaults.conf. Name them apple.cer and windows.cer.
  • Add this to defaults.conf:
    app {
      mac.certificate = apple.cer
      windows.certificate = windows.cer

If you're shipping to macOS you need to configure Apple notarization. Learn how to set up notarization.

  • Run conveyor make site or build unpackaged apps again. Your apps should now be signed and notarized.

Learn more about keys and certificates

Become a 🐢 tortoise

You will probably not be satisfied with the feature set shown in this short tutorial. The rest of the documentation awaits!