Microsoft said on 22 October 2026 that SharePoint can create, upload, edit and publish HTML pages, storing them in the Site Pages library alongside modern pages. Authors can draft an HTML page with Copilot in SharePoint or bring existing HTML into the SharePoint publishing flow.
Some functionality is introduced gradually to organisations that have opted in to the Microsoft Frontier program, so tenants may not see every option. HTML pages are enabled by default, unless a site owner has turned off HTML files for that site.
What authors can do
Authors can start from + New on a SharePoint site, + Create on the Publish landing page, or Create or upload in the Site Pages library. A document library also has Edit in SharePoint for existing HTML files.
Copilot in SharePoint can create a draft from a prompt and attached files. It can also make broader content and design changes through the Copilot chat pane. Authors can edit text on the page itself, and HTML pages use draft and publish states like modern pages.
Upload works for a single HTML file or an HTML folder. SharePoint copies embedded or included non-HTML content, such as images and videos, into Site Assets. When an existing HTML file is edited in SharePoint or moved to Site Pages, it no longer remains in the original document library.
Content and publishing limits
HTML pages can include images, videos, animations and live data that refreshes from SharePoint lists, Excel and CSV files. SharePoint supports Chart.js, Mermaid, React, Fluent UI and Babylon from a Microsoft-managed content delivery network. It also supports JavaScript when the code is contained in the same HTML file.
The maximum size for an HTML file uploaded to the Site Pages library is 10 MB. That limit excludes assets such as images and videos, because SharePoint copies those assets to Site Assets during upload.
The support page lists several limits that communications teams will need to account for. HTML pages cannot be promoted to news posts, amplified to Teams and Viva Engage, saved as templates or scheduled. Co-authoring, private drafts, reactions and comments are also not supported.
Licensing and administration
A Microsoft 365 Copilot license is required for the Copilot authoring experiences, including creating or editing a page with the Copilot chat pane. Uploading or moving HTML content, editing page content directly, publishing, sharing and viewing published pages use existing SharePoint permissions and do not require a Microsoft 365 Copilot license.
Site owners can allow or disallow HTML files for an individual site from the Site Pages library. They use File types on the command bar and switch Allow HTML files on or off. Microsoft says there is no tenant-level control to disallow or restrict HTML pages.
Sandbox and external content
SharePoint renders HTML pages in a sandboxed iframe that isolates the page from the surrounding SharePoint header, footer and navigation. Content Security Policy rules add further isolation. SharePoint blocks arbitrary fetch requests and outbound API calls from HTML pages, does not support cross-tenant communication and does not allow the sandbox to access browser localStorage.
CDN-hosted scripts are not supported, apart from the Microsoft-managed versions of the listed libraries. If a link on an HTML page does not open, a site admin may need to add the domain to the site's allow list under HTML Field Security.
Pages created with Copilot use the site's branding. SharePoint does not automatically apply site branding to uploaded HTML, although authors can ask Copilot in SharePoint to update the page to match the site.
For SharePoint teams, the feature narrows the gap between modern pages and hand-built HTML, but it is not a general web hosting surface. It is a SharePoint publishing surface with page permissions, site-level controls and a constrained sandbox. That distinction matters for intranet owners who need more flexible pages but cannot allow arbitrary client-side code or external calls.
Whether SharePoint authors should use Copilot to generate HTML pages, how site owners control HTML files and which publishing limits remain are practical questions in ECS's M365 + Copilot topic, alongside Teams, SharePoint, Viva, governance and adoption. Sessions and workshops give attendees a place to compare rollout patterns, admin controls, licensing boundaries and content governance from current Microsoft 365 work. Attend with the tenant scenarios and publishing requirements that are difficult to settle from documentation alone.
Photo: Coolcaesar, CC BY-SA 4.0, via Wikimedia Commons, cropped
This article was written by the ECS editorial team with the assistance of Amal Agent, run.events' AI assistant, which supported the research, drafting and proofreading.