| page_type | sample | ||||
|---|---|---|---|---|---|
| products |
|
||||
| languages |
|
||||
| extensions |
|
Explore the List Formatting gallery
Make SharePoint and Microsoft Lists work beautifully with community-built, copy-ready JSON formats. Customize individual columns, transform list and library views, or give forms a more useful layout.
Find a format, check its requirements, copy the JSON, and make it yours. You do not need to clone the repository to use a sample.
Important
This is a community effort maintained with the Microsoft 365 & Power Platform Community. Samples are provided as-is, are not officially supported Microsoft products, and do not include a service-level agreement. Check prerequisites and test every format in your own environment before using it in production.
- Explore: browse the gallery or the source folders below.
- Check the requirements: review the sample's README, column types and internal names, view settings, platform compatibility, and permissions.
- Choose a definition: some samples provide multiple styles or separate form Header, Body, and Footer files. Select the variant you actually need.
- Copy the complete JSON: use Copy JSON or Download JSON in the updated gallery, or copy the definition directly from GitHub.
- Apply and adapt: use the appropriate formatting panel, replace any tenant-specific values, preview the result, and save. Keep a copy of your previous format so you can restore it.
| Format | Source | Where to apply it |
|---|---|---|
| Column | Column samples | Format this column > Advanced mode; see applying column formats |
| View | View samples | Format current view; see applying view formats |
| Form | Form samples | Edit form > Configure layout > the matching Header, Body, or Footer; see applying form formats |
Formats differ in their requirements and supported SharePoint versions. Some actions update data, delete items, or run flows. Understand those actions before using them. Formatting is not a security control: hiding a value visually does not remove access to the underlying data.
Browsing the gallery is free. Individual samples may require licenses, permissions, flows, API keys, or third-party services of their own; check the sample's requirements before use.
The updated gallery provides:
- Screenshot-first browsing with search, sample-type filters, categories, compatibility, contributors, and advanced formatting filters.
- A page for each sample with setup guidance, source links, full definitions, variant selection, and complete copy/download actions.
- Getting-started guides, a formatting reference, and editing/deployment tools.
- Contributors with GitHub profile images and links to their shared formats.
- A What's new timeline based on sample creation and update metadata.
- Light and dark themes, responsive layouts, and accessible navigation.
The original sample READMEs and JSON files remain the source of truth. Automated gallery checks do not prove that every sample works in every tenant.
New samples, improvements, documentation fixes, screenshots, accessibility work, and issue reports are welcome. First-time contributors are encouraged to join in.
- Search the gallery and existing issues to avoid duplicating work.
- Read the Contribution Guidance and creating a sample guide.
- Fork the repository, branch from
master, and keep the pull request focused on one sample or one logical improvement. - Include the sample's README, JSON definitions, local preview image, and
assets/sample.jsonmetadata. Document each variant's requirements and application destination. - Follow the contribution checklist, test changed formats in SharePoint, and describe what you tested in your pull request.
Start with the column, view, or form README template and the sample metadata template. You can also help by improving the documentation or contributing to tools.
An approved code or documentation contribution can qualify you for the Community Contributor - Microsoft 365 & Power Platform Community badge, subject to the published criteria.
See the Credly badge and earning criteria and the Community Recognition Program for registration, eligibility, and how recognition is issued. An accepted pull request does not mean a badge is issued instantly or automatically.
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
Learn together, ask questions, and share what you have built:
- Community Home - explore community initiatives for Copilot, Microsoft 365, and Power Platform.
- Community calls - see the schedule and download recurring invitations. Everyone is welcome.
- Community YouTube channel - watch tutorials, demos, and call recordings.
- List Formatting video playlist
- go deeper into formatting-specific patterns.
- Present a community demo - share your solution and help others learn.
- Getting started with the samples
- Column formatting documentation
- View formatting documentation
- Configure the list form
- Conditionally show or hide form columns
- Formatter helper tools, including SP Formatter and Jsonify
- Advanced deployment with VS Code, PowerShell, and CLI for Microsoft 365
For a problem with a particular sample, review its README, search existing issues, then use the repository issue forms. Include the sample path, reproduction steps, expected behavior, and relevant environment details. Do not post credentials, access tokens, or private tenant data.
For general SharePoint product or tenant issues, use Microsoft documentation, your Microsoft support channel, or the appropriate product community rather than treating a community sample as an officially supported product. See the issue and support guidance. Community help is voluntary and provided on a best-effort basis.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This repository is licensed under the MIT License.
SAMPLES AND DOCUMENTATION ARE PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
Sharing is caring!