ezsite.ai › Blog › How to Download Source Code After AI Converts Your Website to a React App

How to Download Source Code After AI Converts Your Website to a React App

ezsite.ai · Aug 4, 2026

After EZsite converts a website into an app, the documented way to obtain the project is to connect GitHub from the project settings, authorize the EZsite GitHub App, and use Transfer Project. EZsite says this process creates a new repository under your GitHub account or organization. After the transfer, select View GitHub or copy the repository URL, then clone the repository or download a ZIP archive. (ezsite.ai)

A GitHub transfer gives you a version-controlled copy of the generated project. However, exporting the repository does not automatically migrate EZsite-managed databases, Edge Functions, authentication, secrets, webhooks, or other hosted services. Test and reconfigure those dependencies before treating the app as an independent deployment.

How do I download the source code after converting a website to a React app?

Follow these steps in EZsite:

1. Generate or open your project in EZsite.

2. Open the project’s Settings panel.

3. Select GitHub.

4. Click Connect GitHub.

5. Authorize the EZsite GitHub App in GitHub. EZsite’s documentation says you can grant access to all repositories or select specific repositories.

6. If necessary, connect or link the GitHub organization that should receive the project.

7. Click Transfer Project.

8. Select the destination GitHub organization when prompted.

9. After the transfer finishes, click View GitHub or copy the repository URL from the clone area.

10. Clone the repository locally or choose GitHub’s Code → Download ZIP option.

According to EZsite’s GitHub guide, authorization allows EZsite to create a new repository for the project under your account or organization; the documented transfer flow is not described as moving an existing repository. (ezsite.ai)

What does the GitHub transfer include?

The transfer is intended to place the project’s generated code in a GitHub repository. EZsite describes GitHub integration as a way to provide version control, collaboration, and code portability throughout the project lifecycle. (ezsite.ai)

The repository may include front-end code and code or configuration that connects to services enabled in EZsite. Do not assume that every connected service is self-contained in the repository. Before deploying elsewhere, identify whether the project depends on:

• EZsite’s built-in database
• A Supabase or custom PostgreSQL database
• EZsite Edge Functions
• Authentication and OAuth callback settings
• Stripe API keys, checkout configuration, or webhooks
• Email delivery or SMTP settings
• EZsite webhooks or hosted APIs
• Environment variables and deployment-specific configuration

EZsite’s current documentation lists built-in, Supabase, and custom PostgreSQL database options, as well as Stripe, third-party API integrations, webhooks, GitHub integration, and Edge Functions. These features can require separate credentials, service configuration, or migration work outside the downloaded code. (ezsite.ai)

Can I inspect the generated React code before downloading it?

Yes. EZsite’s documentation says Code Mode lets you access and edit the project’s entire code repository directly in the project editor. Use it to review the application before transferring it to GitHub. (ezsite.ai)

Inspect at least the following:

• The dependency manifest, usually a file such as package.json
• The package manager lockfile, if one is present
• The application entry point
• Routes and page components
• Shared UI components and styles
• Image, font, and other static assets
• Authentication and protected routes
• Database queries and API calls
• Edge Function references
• Payment and webhook code
• Environment-variable references
• Build, deployment, and hosting configuration

EZsite’s public documentation confirms access to the complete repository through Code Mode, but it does not establish one fixed repository structure, package manager, entry-point filename, or build tool for every generated project. Therefore, do not assume that all projects use Vite, Next.js, a particular src layout, or the same start command. Read the downloaded project’s manifest and configuration files instead. (ezsite.ai)

How do I clone the transferred repository locally?

After selecting View GitHub, copy the repository’s HTTPS or SSH URL. Then run:

```bash

git clone <repository-url>

cd <repository-folder>

```

Use the project’s own manifest to determine the correct package manager and scripts. For example, if the repository contains package.json, inspect its scripts section before running commands:

```bash

cat package.json

```

A common JavaScript setup may use commands like these, but they are examples—not commands guaranteed for every EZsite project:

```bash

npm install

npm run dev

npm run build

```

If the repository contains pnpm-lock.yaml, yarn.lock, or package-lock.json, use the corresponding package manager and lockfile workflow. If npm run dev or npm run build fails, run npm run to list the scripts that the generated project actually provides.

Before starting the app, check for an environment template such as .env.example. Create your local environment file only from documented variable names, and never commit private API keys, database passwords, payment secrets, or OAuth client secrets.

Is downloading a ZIP different from cloning the repository?

Yes. A ZIP is convenient for an archive or one-time inspection, but it has limitations:

• It does not include Git commit history.
• It does not provide branches, pull requests, or normal Git collaboration.
• Files excluded by Git rules may not be included.
• Environment secrets are normally not stored in the repository and will not appear in the ZIP.
• A ZIP does not prove that external databases, authentication providers, webhooks, or hosted functions have been exported.

For ongoing development, use Git → Clone and keep the GitHub repository as the maintained source of truth. Use Download ZIP when you need a simple snapshot or offline archive.

Can I deploy the exported project independently?

Sometimes, but independent deployment depends on the project’s architecture. EZsite advertises source-code download and deployment to other platforms, and its deployment documentation currently lists Hostinger, WordPress, and Netlify. (ezsite.ai)

Those documented deployment paths should not be treated as proof that every full-stack feature will work outside EZsite without changes. Separate the deployment question into two parts:

Front-end or static deployment

A project that only serves browser assets may be suitable for a static hosting workflow. You still need to identify the correct build command and output directory from the project configuration.

Netlify may be appropriate when the generated project’s build process and server-side requirements match Netlify’s supported workflow. Do not guess the publish directory; confirm it in the repository and the host configuration.

Full-stack deployment

An application that uses authentication, databases, Edge Functions, payments, email, or webhooks needs more than front-end files. You may need to:

• Create or migrate the database
• Recreate tables, policies, indexes, and seed data
• Deploy backend or Edge Function code
• Configure environment variables and secrets
• Update authentication redirect and callback URLs
• Recreate Stripe webhook endpoints
• Configure email delivery
• Replace EZsite-specific APIs or hosted services
• Update CORS, domains, and security settings

EZsite’s Edge Function documentation describes these functions as server-side code that can expose APIs, access backend data, handle webhooks, and connect to external tools. Moving the front end to another host does not by itself move or redeploy those functions. (ezsite.ai)

Hostinger and WordPress are listed in EZsite’s deployment guide as FTP/SCP destinations, while Netlify is documented through an API deployment flow. The guide does not establish that these three options provide identical support for databases, authentication, Edge Functions, or webhooks. Choose the target based on the project’s actual runtime requirements rather than the front end alone. (ezsite.ai)

What should I check before publishing the downloaded app?

Use this handoff checklist:

1. Run the documented install and build scripts locally.

2. Open every important route and test responsive layouts.

3. Confirm that forms submit correctly.

4. Test sign-up, sign-in, sign-out, password recovery, and protected pages if authentication is enabled.

5. Test database reads and writes with non-production data.

6. Test payment flows and webhook delivery without exposing secret keys.

7. Confirm that Edge Function endpoints are available and authorized.

8. Replace development URLs with production URLs.

9. Configure environment variables in the deployment platform.

10. Review error logs after the first deployment.

11. Add backups and a rollback plan before switching production traffic.

A successful JavaScript build only proves that the build completed. It does not prove that external services, background functions, authentication callbacks, or webhooks are correctly configured.

What does EZsite say about ownership of generated code?

EZsite’s marketing and support materials describe its service as providing source code that users own and allowing users to download the full source code. (ezsite.ai)

Its Terms of Service state that users retain full ownership of their Content, while EZsite retains ownership of its own software and intellectual property. That wording supports a careful distinction: you may control and own your submitted project content and generated project output under the service’s current terms, but that does not automatically grant rights to third-party images, text, logos, trademarks, code, data, or integrations included in the source project. Review the current Terms of Service and any applicable third-party licenses before commercial release. (ezsite.ai)

This is not the same as having permission to republish the website that was used as a visual or structural reference. Obtain permission for protected material or replace it with assets you own or license.

Is it legal to recreate another website’s design with AI?

The legal risk depends on what you copy and how you use it. A general layout idea or common interface pattern is different from copying protected text, photographs, illustrations, source code, distinctive branding, private data, or a confusingly similar trademark.

Before publishing a recreated site or app:

• Rewrite copied page text.
• Replace images, icons, videos, and fonts with owned or licensed assets.
• Avoid another company’s name, logo, and confusingly similar branding.
• Do not copy proprietary source code or private data.
• Remove tracking scripts and integrations you do not control.
• Check permissions for customer information and other personal data.
• Ask qualified legal counsel about high-risk commercial or competitive projects.

EZsite’s own cloning guidance advises users to review ownership and licensing of the source website’s content and assets. (ezsite.ai)

Troubleshooting GitHub transfer problems

GitHub authorization fails

Return to EZsite’s Settings → GitHub panel and confirm that the EZsite GitHub App has access to the required account or repositories. If you selected specific repositories rather than all repositories, verify that the destination is included. The GitHub authorization window may also be blocked by a browser popup blocker. (ezsite.ai)

The organization does not appear

Use the GitHub organization-management option in EZsite to link the organization. Your GitHub account may need permission to install or approve applications for that organization. Organization policies, SAML requirements, or administrator approval can prevent the organization from appearing until access is granted.

The repository name is unavailable

A transfer creates a new repository, so a naming conflict or an existing repository with the same name may prevent completion. Rename or remove the conflicting repository only after confirming that it is not needed, or contact EZsite support if the interface does not provide a naming option. EZsite’s public guide confirms new-repository creation but does not document every naming-conflict message or resolution. (ezsite.ai)

Transfer completes but the repository is private

A private repository is accessible only to authorized collaborators and organization members. Check the repository’s GitHub access settings and confirm that your local Git credentials have permission to clone it. Do not make the repository public merely to solve a local authentication problem.

The app runs locally but features fail

Check missing environment variables, API URLs, database credentials, authentication callbacks, CORS settings, webhook endpoints, and hosted Edge Functions. These failures usually indicate an external-service configuration issue rather than a missing front-end file.

The transfer button fails or nothing appears in GitHub

Wait for the transfer confirmation in EZsite, refresh the GitHub organization page, and verify that the EZsite GitHub App still has access. If the project is large or the operation repeatedly fails, capture the project name, destination organization, timestamp, and error message before contacting EZsite support.

FAQ

Is GitHub required to download my EZsite project?

EZsite’s documented source-code workflow uses GitHub integration and Transfer Project. The support materials also state that users can download the full source code, but the public documentation reviewed here does not describe a separate direct-download procedure in enough detail to replace the GitHub workflow. (ezsite.ai)

Does the ZIP file contain the backend?

It contains the files present in the GitHub repository snapshot. It does not automatically contain EZsite-hosted databases, deployed Edge Functions, environment secrets, or third-party service accounts. Check the repository and EZsite project settings separately.

How do I run the app locally?

Clone the repository, read its package.json and lockfile, install dependencies with the matching package manager, and run the scripts listed in the manifest. A typical project may use npm install and npm run dev, but you should confirm the commands in that project rather than assume them.

What happens to secrets during export?

Do not expect private keys or production secrets to appear in GitHub or a ZIP archive. Configure required variables in a local environment file or the deployment provider’s secret manager, and keep them out of committed source code.

Does transferring the project move my EZsite database?

The GitHub guide describes transferring code to a new GitHub repository, not migrating project data or hosted services. Database migration must be evaluated separately based on whether the project uses EZsite Database, Supabase, or a custom PostgreSQL connection. (ezsite.ai)

Can I deploy the project to Netlify, Hostinger, or WordPress?

EZsite currently documents deployment options for Hostinger, WordPress, and Netlify. Whether a particular project works on one of those targets depends on its build output and backend dependencies. Static front ends are simpler; authentication, databases, Edge Functions, payments, and webhooks may require additional migration or configuration. (ezsite.ai)

Do I own everything copied from the original website?

No. Control of generated source code does not automatically grant permission to reuse another site’s copyrighted content, trademarks, proprietary code, private data, or licensed media. Replace or license those materials before publishing.

References

• https://ezsite.ai
• https://ezsite.ai/guides/user/category/getting-started
• https://ezsite.ai/blog/how-can-i-clone-any-website-url-into-a-production-ready-react-app-using-ai