Edge Developer Platform
  • Pages
    • Product Introduction
    • Quick Start
      • Importing a Git Repository
      • Starting From a Template
      • Direct Upload
    • Framework Guide
    • Project Guide
      • Project Management
      • edgeone.json
      • Configuring Cache
      • Error Codes
    • Build Guide
    • Deployment Guide
      • Overview
      • Create Deploys
      • Manage Deploys
      • Deploy Button
      • Use Github Actions
      • Using CNB Plugin
      • Using IDE Plug-In
      • Using CodeBuddy IDE
    • Domain Management
      • Overview
      • Custom Domain Name
      • Configuring an HTTPS Certificate
      • How to Configure a DNS CNAME Record
    • Pages Functions
    • KV Storage
    • Edge AI
    • API Token
    • EdgeOne CLI
    • Pages MCP
    • Integration Guide
      • AI
        • Dialogue Large Models Integration
        • Large Models for Images Integration
      • Database
        • Supabase Integration
        • Pages KV Integration
      • Ecommerce
        • Shopify Integration
        • WooCommerce Integration
      • Payment
        • Stripe Integration
        • Integrating Paddle
      • CMS
        • WordPress Integration
        • Contentful Integration
        • Sanity Integration
      • Authentication
        • Supabase Integration
        • Clerk Integration
    • Best Practices
      • Using General Large Model to Quickly Build AI Application
      • Use the Deepseek-R1 model to quickly build a conversational AI site
      • Building an Ecommerce Platform with WordPress + WooCommerce and GatsbyJS
      • Building a SaaS Site Using Supabase and Stripe
      • Building a Company Brand Site Quickly
      • How to Quickly Build a Blog Site
    • Migration Guides
      • Migrating from Vercel to EdgeOne Pages
      • Migrating from Cloudflare Pages to EdgeOne Pages
      • Migrating from Netlify to EdgeOne Pages
    • Troubleshooting
    • FAQs
    • Contact Us
    • Release Notes

Direct Upload

You can upload the project build assets directly to Pages and deploy it to EdgeOne global network. If you want seamless integration with your own build platform or upload from a local computer, you should select direct upload rather than import Git repository.
Note:
If you select direct upload, you will be unable to switch to Git integration later. You must create a new project with Git integration to use automatic deployment.


Creates a project.

Go to the Pages console homepage, select "Create project", then choose "Direct upload".


After filling in the "project name" and "acceleration region", drag and drop the project asset to the designated region.

Click "Start deployment". After uploading the asset, the project creation will begin, then navigate to the deployment details page. After successful deployment, you can view the project through the preview URL.


Creating a New Deployment

After creating a project, you can release a new version by selecting "Create New Deployment" on the deployment page.

Drag and drop the new version of the project asset to the designated region. The deployment environment defaults to "production environment" and can be switched to "preview environment."

Note:
Live production environment: Update to the website users access, effective immediately.
Preview environment: Verify changes in an isolated environment without affecting official data.


Upload Limit

The project asset limit is 1000 files with a single file size of 25MB.
If the limit is exceeded, a red warning will appear in the upload area. You can adjust the project assets and reupload. Alternatively, use the EdgeOne CLI deploy command for upload deployment. The specific operation method can be found in the Documentation.


Supported File Types

Direct upload currently supports a single ZIP compressed package or single folder.


Functions and Edgeone.Json

Direct upload also supports Pages Functions and the project config file edgeone.json. You just need to place the functions folder and edgeone.json in the root directory.

For more information about functions, view Pages Functions document.
Note:
Note: For direct upload, the edgeone.json file support only redirects, rewrites, headers, and caches settings. For details, see edgeone.json document.