Product Introduction
Quick Start
- Importing a Git Repository
- Starting From a Template
- Direct Upload
Framework Guide
- Frontends
- Backends
- Full-stack
  - Next.js
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
- Configuring an HTTPS Certificate
- How to Configure a DNS CNAME Record
Pages Functions
- Overview
- Edge Functions
- Node Functions
Log Analysis
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 the EdgeOne global network. If you want to integrate your own build platform or upload from a local computer, you should select direct upload rather than import a 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.
On the Pages console homepage, select "Create project" and 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 assets, project creation will begin. Subsequently, 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 Deployment" on the deployment page.
﻿
Drag and drop the new version of the project asset to the specified region. The deployment environment defaults to "production environment" and can be switched to "preview environment."
﻿
Note:
Live production environment: Update to the user access website, 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 deployment. For specific operation methods, see Documentation.
﻿
Supported File Types
Direct upload currently supports one ZIP compressed package or one folder.
﻿
Functions and Edgeone.Json
Direct upload likewise supports Pages Functions as well as the project config file edgeone.json. You only need to place the edge-functions and node-functions folders as well as edgeone.json in the root directory.
﻿
For more information about functions, view the Pages Functions document.
Note:
Note: For direct upload, the edgeone.json file supports only redirects, rewrites, headers, and caches field settings. For details, see edgeone.json document.
﻿

Creates a project.
Creating a New Deployment
Upload Limit
Supported File Types
Functions and Edgeone.Json