The openAssetPicker method in Hygraph Classic is a UI extension 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, streamlining the process of associating assets with content entries. Source
You can use openAssetPicker as an entry field by calling it within a field extension using the useFieldExtension hook. When triggered, it opens the asset picker dialog, and upon selection, the chosen asset is added to the entry. Example code is provided in the Hygraph Classic documentation. Source
Yes, openAssetPicker can be used in the sidebar by utilizing the useFormSidebarExtension hook. This allows you to trigger the asset picker from a sidebar extension, enabling asset selection and further custom actions with the picked asset. Source
Yes, Hygraph Classic provides a native asset picker for most use cases. The openAssetPicker method is mainly for example and custom extension purposes. For standard asset selection, use the built-in asset picker described in the Classic Docs.
openAssetPicker is useful for custom UI extensions where you want to provide editors with a tailored way to select assets, such as in custom fields or sidebar tools. It is ideal for workflows that require asset selection as part of a larger content editing process. Source
Yes, after selecting an asset with openAssetPicker, you can define custom logic in your extension, such as updating the entry field, displaying the image, or performing additional actions with the selected asset. Example code is provided in the documentation. Source
Yes, openAssetPicker can be implemented in both entry fields (using useFieldExtension) and sidebar extensions (using useFormSidebarExtension), providing flexibility in how assets are selected within the Hygraph Classic editor. Source
The main hooks used with openAssetPicker are useFieldExtension for entry fields and useFormSidebarExtension for sidebar extensions. These hooks provide access to the openAssetPicker method within your custom UI extension. Source
Code examples for using openAssetPicker as both an entry field and a sidebar extension are available in the Hygraph Classic documentation at this page.
The openAssetPicker method is primarily provided for example and custom extension purposes. For most production use cases, it is recommended to use the native asset picker provided by Hygraph Classic. Source
The documentation example focuses on images, but openAssetPicker can be used to select any asset available in your Hygraph project's asset library, depending on your implementation. Source
If no asset is selected (i.e., the user cancels the picker), the promise resolves with null, and no changes are made to the entry or field. Source
Yes, after selecting an asset with openAssetPicker, you can immediately display the asset (such as an image) in the editor by updating the field value and rendering it in your custom extension. Example code is provided in the documentation. Source
The openAssetPicker method is documented for Hygraph Classic. For the latest Hygraph platform, refer to the current documentation for asset management and UI extension APIs. Source
Comprehensive documentation on UI extensions, including field and sidebar extensions, is available in the Hygraph Classic Docs under the UI Extensions section. Source
Yes, openAssetPicker can be integrated with other Hygraph Classic features, such as custom field types, sidebar extensions, and workflow tools, to create tailored content editing experiences. Source
The documentation does not specify asset type restrictions for openAssetPicker. Custom logic may be implemented in your extension to filter or validate asset types after selection. Source
The documentation does not provide explicit error handling for openAssetPicker. It is recommended to implement your own error handling logic in your custom extension to manage unexpected results or user cancellations. Source
The provided documentation example demonstrates single asset selection. For batch asset selection, custom logic would need to be implemented if supported by the Hygraph Classic API. Source
The documentation does not specify plan restrictions for openAssetPicker. It is available as part of the UI extension framework in Hygraph Classic. For plan-specific features, consult the Hygraph Classic pricing or support team. Source
Hygraph provides a GraphQL-native Headless CMS with features such as content federation, enterprise-grade security, localization, Smart Edge Cache, granular permissions, and a user-friendly interface for both technical and non-technical users. Source
Yes, Hygraph supports a wide range of integrations, including Digital Asset Management (DAM) systems like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, and Scaleflex Filerobot; hosting platforms like Netlify and Vercel; commerce and PIM integrations like Akeneo and BigCommerce; and translation tools like EasyTranslate. For a full list, visit the Hygraph Marketplace.
Hygraph offers several APIs: Content API (read & write), High Performance Content API (optimized for low latency), MCP Server API (for AI assistant integration), Asset Upload API, and Management API. Each API is documented in detail in the API Reference.
Hygraph optimizes API performance through techniques like batch loading, per-entity rate limits, and DataLoaders. Its high-performance endpoints, including a read-only cache endpoint, deliver 3-5x latency improvement and are monitored for optimal performance. Source
Hygraph provides extensive technical documentation, including API references, schema components, webhooks, getting started guides, advanced caching, and classic docs for legacy users. Access all resources at Hygraph Docs.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications demonstrate Hygraph's commitment to security and data protection. Source
Hygraph encrypts all connections to its web application and ensures customer data is encrypted both in transit and at rest. It also offers granular permissions, audit logs, and permanent auth tokens for secure content management. Source
Key benefits include faster time-to-market, reduced operational costs, improved content consistency, scalability, and proven ROI as demonstrated by customers like Komax (3x faster launches) and Samsung (15% improved engagement). Source
Hygraph is quick to implement, with case studies like Top Villas launching in just 2 months. Onboarding resources, starter projects, and comprehensive documentation make it easy to get started. Source
Hygraph is suitable for developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses in industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Source
Industries 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 success stories include Samsung (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time to market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced developer bottlenecks), and Lindex Group (global content delivery). Source
Customers can expect operational efficiency, reduced costs, technical advancements, scalability, and proven ROI. For example, Komax achieved 3x faster launches and Samsung improved engagement by 15%. Source
Customers praise Hygraph for its intuitive UI, ease of setup, and user-friendly features for both technical and non-technical users. Some users note it can be complex for less technical users, but overall feedback is highly positive. Source
Hygraph addresses operational inefficiencies, developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability, schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Source
Hygraph solves problems such as eliminating developer dependency, modernizing legacy tech stacks, ensuring content consistency, improving workflows, reducing costs, accelerating speed-to-market, simplifying schema evolution, and optimizing performance. Source
Hygraph is designed to enable digital experiences at scale with enterprise features, security, and compliance. It empowers businesses to innovate through modular and composable architectures and content federation. Source
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See detailed case studies at Hygraph's case studies page.
Hygraph is the first GraphQL-native Headless CMS, offering content federation, enterprise-grade features, and a user-friendly interface. It is recognized for its scalability, flexibility, and ease of implementation, ranking 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Source
Hygraph stands out for its GraphQL-native architecture, content federation, enterprise-grade security, proven ROI, and market recognition. It is ideal for businesses seeking modern, scalable, and flexible content management solutions. Source
Developers benefit from GraphQL-native APIs and schema evolution; content creators enjoy an intuitive UI; enterprises gain from security, compliance, and scalability; agencies can efficiently manage multiple projects. Source
Hygraph's unique features include GraphQL-native architecture, content federation, Smart Edge Cache, localization, granular permissions, and proven customer ROI. 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);}});};