3Edit Web Builder iconLesson 16 · Save, publish and launch

Move your project to another computer

Bring it across, reconnect it, and carry on where you left off.

A new laptop, or a second computer? Learn the two ways to bring your 3Edit project across, a downloaded .zip or your GitHub, what comes with it, and what to reconnect afterwards.

About 6 minutes to readLast updated

By Humayun Rashed, founder of 3Edit

What a project is made of

Your 3Edit project lives on your computer: its files, its chat and its Project History. Your data lives somewhere else: in your own Supabase, online, so it is the same database whichever computer you use.

That makes moving straightforward. You bring the project across, then reconnect it to the services it uses.

Two ways to move

Both ways create a new project on the other computer. Choose the one that suits you.

Download and Restore BackupImport from GitHub
You needAn active planA plan, and GitHub connected
On your first computerPress Download project, the download icon above the preview, to save a .zipNothing more: your latest save is already on GitHub
On the other computerPress Restore Backup on the projects screen and choose the .zipPress Import from GitHub
What you getA new project with its chat and Project HistoryA new project from its latest saved code, without the local Project History

What stays behind, on purpose

The env files where keys live are left out of the download, so secret keys never travel inside a .zip. Keys belong in each service’s own secure settings, as Keys, server routes and keeping secrets safe explains.

Keys saved in your store’s own admin settings are different: they live in your database, so they come back with it.

Reconnect on the other computer

Once the project is open on the other computer, reconnect it to the services it uses.

  1. SupabaseReconnect your Supabase. It is the same database, so every account and all your data are still there.
  2. Your keysEnter the keys you saved in 3Edit’s key form again, on this computer.
  3. Hosting and domainReconnect your hosting and your domain, so publishing updates the same live site.
  4. GitHubSign in to GitHub again, so your saves keep reaching your repository.

Work on one computer at a time

“Work on one computer at a time; your latest save is always kept on GitHub.” Finish and save on one computer before you carry on with the other, so you always build on your newest work.

Import from GitHub always creates a new project. Pulling GitHub changes into an open project is coming in an update.

Good habits when you move

  • Download a fresh copy just before you move: the .zip then holds your newest work, chat and Project History.
  • Keep your keys somewhere safe: you enter them again on the other computer, so keep them in a password manager, never in a document or a chat.
  • Check before you change anything: open the preview, sign in with a test account and make sure your data is there.
  • Publish again only when it’s all reconnected: hosting, domain and keys first, then publish.

Try it in 3Edit.

These prompts get any project ready to move, such as the booking request site from Does my website need a database?. Read Versions, backups and GitHub first, and connect GitHub if you’d like to use Import from GitHub.

The businesses in these prompts are fictional practice examples. When you build for a real business, only ever show real reviews from real customers: invented reviews mislead customers and are against UK consumer law.

  1. 1What to reconnect

    I’m moving this project to another computer. List every outside service it uses, such as the database, email, payments, hosting and domain, and for each one say what I’ll need to reconnect or enter again. Don’t include any key values.

  2. 2A moving checklist

    Write a short checklist I can follow on the other computer after I restore this project: what to reconnect, which pages to check, and one test sign-in to try. Keep it under 12 lines.

  3. 3Check after the move

    I’ve just restored this project on another computer and reconnected Supabase. Check that the pages that read from the database still load, and tell me if anything still needs a key. Don’t change anything yet.

Then try it for real: press Download project above the preview, and on the other computer press Restore Backup on the projects screen. Reconnect each service on your checklist before you publish again.

Questions people ask.

Press Download project, the download icon above the preview, to save a .zip. On the other computer, press Restore Backup on the projects screen and choose the file. Or, with GitHub connected, use Import from GitHub.

Yes. Download project needs an active plan, and Import from GitHub needs a plan and GitHub connected.

They stay where they are, in your own Supabase. Reconnect the same database on the other computer, and every account and all your data are there.

No. The env files with keys are left out, so you enter the keys you saved in 3Edit again on the other computer. Keys saved in your store’s own admin settings live in your database, so they come back with it.

Restore Backup creates a new project from a downloaded .zip, with its chat and Project History. Import from GitHub creates a new project from your latest saved code on GitHub, without the local Project History.

Yes, one at a time. Work on one computer at a time; your latest save is always kept on GitHub.

Start vibe coding today.

Download 3Edit for Mac or Windows and build your first professional website in minutes.

Download now
macOSWindows