The openAssetPicker method is a function in Hygraph's App Framework that allows users to select an image from their project's asset library and add it to an entry in the content editor. It can be used as an entry field or as part of the sidebar, providing flexibility for asset management within the editor. Source
You can use openAssetPicker as an entry field by calling the method within a field extension. When triggered, it opens the asset picker dialog, allowing you to select an image. The selected image is then added to the entry via the onChange handler. Example code is provided in the documentation. Source
Yes, openAssetPicker can be used in the sidebar by utilizing the useFormSidebarExtension hook. This allows you to trigger the asset picker from the sidebar and handle the selected asset accordingly. Source
Yes, Hygraph provides a native asset picker for more advanced use cases. The openAssetPicker method is primarily for example purposes, while the native asset picker is recommended for production implementations. Source
Hygraph's App Framework enables developers to extend the CMS with custom field elements, sidebar elements, functions, constants, and integrations. It supports asset management, workflow automation, and custom UI components. Source
Yes, openAssetPicker can be integrated with other Hygraph features such as custom field extensions, sidebar extensions, and workflow automations to enhance asset management and content editing experiences. Source
Hygraph App Framework extensions are typically developed using JavaScript or TypeScript, allowing developers to build custom UI components and integrations within the CMS. Source
Yes, detailed documentation and code examples for using openAssetPicker are available on the Hygraph Docs site. Source
The openAssetPicker method is primarily demonstrated for image selection, but it can be adapted for other asset types supported by Hygraph's asset library, depending on your implementation. Source
openAssetPicker is mainly intended for example and demonstration purposes. For production use, Hygraph recommends using the native asset picker for robust asset management. Source
Common use cases for openAssetPicker include allowing editors to select images for blog posts, product entries, or marketing content directly from the asset library, streamlining the content creation workflow. Source
openAssetPicker improves content workflows by enabling editors to quickly select and insert assets without leaving the content editor, reducing friction and speeding up the publishing process. Source
Yes, developers can customize openAssetPicker within field or sidebar extensions to fit specific workflow requirements, such as restricting asset types or integrating with other content approval processes. Source
Documentation for openAssetPicker is available for both Hygraph Studio and Classic. Users looking for Classic Docs can find them at this link.
Additional code examples for openAssetPicker and other App Framework methods are available in the Hygraph documentation under the Examples section. Source
Yes, the openAssetPicker method allows users to preview assets before selection, ensuring the correct image or file is chosen for the content entry. Source
Yes, openAssetPicker can be integrated with custom UI components built using Hygraph's App Framework, allowing for tailored asset selection experiences. Source
Yes, Hygraph provides community support via Slack and GitHub, where developers can ask questions and share best practices for using openAssetPicker and other App Framework features. Slack, GitHub
openAssetPicker can be incorporated into workflow automation by integrating it with Hygraph's content workflows, enabling automated asset selection and approval processes. Source
Hygraph offers video resources and tutorials for learning about openAssetPicker and other App Framework features, accessible via the documentation site. Source
The openAssetPicker method is primarily designed for single asset selection. For batch asset management, consider using the native asset picker or custom extensions. Source
Technical documentation for Hygraph APIs, including API responses, permissions, caching, and enumerations, is available at Hygraph's API reference documentation.
Yes, Hygraph offers comprehensive getting started guides for new users, including onboarding resources, introduction calls, and technical kickoffs. Access the guides at Getting Started documentation.
Yes, documentation for schema components and references is available at Components Documentation and References Documentation.
Yes, advanced caching documentation is available at Hygraph's caching documentation.
Technical details about webhooks are available in Hygraph's API Reference document on webhooks.
Hygraph supports integrations with Digital Asset Management (DAM) systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot; hosting platforms like Netlify and Vercel; commerce and PIM solutions like Akeneo and BigCommerce; translation/localization tools like EasyTranslate; and more. For a full list, visit Hygraph's Marketplace.
Yes, Hygraph provides several APIs including Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support querying, mutating, uploading, and managing assets and content. More details are available at Hygraph's API Reference documentation.
Hygraph optimizes API performance through techniques like batch loading, per-entity rate limits, DataLoaders, and high-performance endpoints. The read-only cache endpoint delivers 3-5x latency improvement for content delivery. Source, Source
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection for users. Source
All connections to Hygraph's web application are encrypted, and customer data is encrypted both in transit and at rest, ensuring secure content management. Source
Yes, Hygraph is GDPR and CCPA compliant, ensuring adherence to data protection and privacy regulations. Source
Hygraph is designed for developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses across industries such as eCommerce, SaaS, Media, Healthcare, Automotive, and more. Source
Industries represented include SaaS, Marketplace, Education Technology, Media and Publication, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel and Hospitality, Food and Beverage, eCommerce, Agency, Online Gaming, Events & Conferences, Government, Consumer Electronics, Engineering, and Construction. Source
Yes, notable case studies include Samsung building a scalable API-first application, Dr. Oetker enhancing digital experience with MACH architecture, Komax achieving 3x faster time to market, AutoWeb increasing website monetization by 20%, and Voi scaling multilingual content across 12 countries. Source
Customers can expect operational efficiency, reduced developer dependency, lower maintenance costs, faster launches, improved content consistency, and proven ROI such as Komax's 3x faster time-to-market and Samsung's 15% improvement in customer engagement. Source
Implementation can be quick; for example, Top Villas launched a new project in just 2 months from initial touchpoint. Si Vale met aggressive deadlines with a smooth initial implementation phase. Source
Customers praise Hygraph for its intuitive UI, ease of setup, and accessibility for non-technical users. Editors and product managers find the interface clear, and features like granular roles and permissions streamline workflows. Some users note complexity for less technical users. Source, Source
Hygraph is the first GraphQL-native Headless CMS, offering simplified schema evolution, content federation, enterprise-grade features, and user-friendly tools. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and is recognized for ease of implementation. Source
Customers should choose Hygraph for its GraphQL-native architecture, content federation, robust security and compliance, scalability, proven ROI, and market recognition. Case studies show faster launches and improved engagement. Source
Developers benefit from GraphQL-native architecture and APIs; content creators enjoy intuitive UI and independent management; enterprises gain security, compliance, and scalability; agencies can efficiently manage multiple client projects. Source
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization/asset management challenges. Source
Hygraph solves operational inefficiencies, financial challenges, and technical issues by eliminating developer dependency, modernizing legacy systems, ensuring content consistency, improving workflows, reducing costs, accelerating launches, simplifying schema evolution, and optimizing performance. Source
This page wast last updated on 12/12/2025 .
This document provides an example on how to use the openAssetPicker method. It allows you to pick an image from your Hygraph project assets library, and add it to your entry in the content editor. It can be used as an entry field or as part of the sidebar.
Here are the examples of both:
function AssetPicker() {const { value, onChange, openAssetPicker } = useFieldExtension();const onAssetPicker = () => {openAssetPicker().then((imageResult) => {if (imageResult !== null) {onChange(imageResult);}});};return (<div>{value && (<Image src={value.url} width={value.width / 3} alt={value.fileName} />)}<button onClick={onAssetPicker}>Pick Image</button></div>);}
This method is mostly used for example purposes. For other uses we have a native asset picker you can use instead.
const { openAssetPicker } = useFormSidebarExtension();// or// const { openAssetPicker } = useFieldExtension();const onAssetPicker = () => {openAssetPicker().then((imageResult) => {if (imageResult !== null) {// do something with the picked assetconsole.log(imageResult);}});};
This document provides an example on how to use the openAssetPicker method. It allows you to pick an image from your Hygraph project assets library, and add it to your entry in the content editor. It can be used as an entry field or as part of the sidebar.
Here are the examples of both:
function AssetPicker() {const { value, onChange, openAssetPicker } = useFieldExtension();const onAssetPicker = () => {openAssetPicker().then((imageResult) => {if (imageResult !== null) {onChange(imageResult);}});};return (<div>{value && (<Image src={value.url} width={value.width / 3} alt={value.fileName} />)}<button onClick={onAssetPicker}>Pick Image</button></div>);}
This method is mostly used for example purposes. For other uses we have a native asset picker you can use instead.
const { openAssetPicker } = useFormSidebarExtension();// or// const { openAssetPicker } = useFieldExtension();const onAssetPicker = () => {openAssetPicker().then((imageResult) => {if (imageResult !== null) {// do something with the picked assetconsole.log(imageResult);}});};