Frequently Asked Questions

Click to Edit Feature & Setup

What is the Click to Edit feature in Hygraph?

Click to Edit lets editors jump from any tagged element in a content preview directly to that field in Hygraph Studio. It is built on top of live preview and enables editors to make changes without developer involvement. Editors can hover over a tagged element, click the Edit button, and update the field in Studio, with changes automatically reflected in the preview. Note: Full visual editing requires both Click to Edit and live preview to be set up. Learn more. Limitation: Click to Edit cannot navigate directly to a field in a specific locale; editors must manually select the target locale within Studio.

How do I set up Click to Edit in my Hygraph project?

To set up Click to Edit, follow these steps: 1) Install the Hygraph Preview SDK (npm install @hygraph/preview-sdk), 2) Create a PreviewWrapper component for your framework (React, Next.js, Remix, Vue, or vanilla JS), 3) Set environment variables for your Content API endpoint, Studio URL, and Permanent Auth Token, 4) Add data-hygraph-* attributes to content elements, 5) Set up the Preview widget in Studio, and 6) Verify the setup by opening an entry and testing the Edit button. Detailed instructions are available in the Click to Edit documentation. Limitation: The feature is currently in Beta and may not support all edge cases.

What frameworks are supported for Click to Edit setup?

Click to Edit supports React, Next.js (App Router and Pages Router), Remix, Vue/Nuxt, and vanilla JavaScript. Implementation examples for each framework are available in the documentation and GitHub repository. Note: Frameworks outside this list may require custom integration. See code examples.

What are the prerequisites for using Click to Edit?

You need a Hygraph project with at least one model and content entry, plus a running preview application (local or deployed) using a supported framework. You must also have access to your Content API endpoint, Studio base URL, and a Permanent Auth Token if authentication is required. Limitation: Projects without a preview application or proper API access cannot use Click to Edit.

How does Click to Edit handle component fields and nested content?

For component fields, you must add the data-hygraph-component-chain attribute, which is a JSON array describing the path from the root entry to the nested component instance. The instanceId is retrieved from your GraphQL query. This enables editors to focus on specific fields within nested components. Limitation: Incorrect configuration of component chains can prevent proper field focus; always use the root entry ID for data-hygraph-entry-id.

What are the known limitations of Click to Edit?

Click to Edit cannot navigate directly to a field in a specific locale. The Edit button opens the correct field in the default locale, but editors must manually select the target locale within Studio. Additionally, the feature is in Beta and may not support all edge cases or frameworks. For troubleshooting, refer to the troubleshooting guide.

How can I troubleshoot issues with Click to Edit?

If Edit buttons do not appear, confirm data-hygraph-entry-id is present, add debug={true} to your PreviewWrapper, and check the browser console. For preview loading issues, verify your endpoint and Studio URL, and check Vercel's X-Frame-Options if using Vercel. For real-time updates, enable sync={{ fieldUpdate: true }}. For component focus issues, ensure the component chain is correctly ordered and instance IDs match your GraphQL query. See troubleshooting details.

Features & Capabilities

What are the key features of Hygraph?

Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and integrations with DAM, hosting, commerce, and translation platforms. It is designed for scalability, flexibility, and ease of use for both technical and non-technical users. Limitation: Detailed limitations not publicly documented; ask sales for specifics. See feature details.

What integrations are available with Hygraph?

Hygraph integrates with Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot (DAM), Netlify, Vercel (hosting), Akeneo (PIM), Adminix, Plasmic, BigCommerce (commerce), and EasyTranslate (translation). For a complete list, visit Hygraph's Marketplace. Limitation: Some integrations may require additional configuration or third-party accounts.

Does Hygraph provide APIs for content and asset management?

Yes, Hygraph offers a GraphQL Content API for querying and manipulating content, a Management API for project structure, an Asset Upload API for uploading files, and an MCP Server API for secure AI assistant communication. Documentation is available at API Reference. Limitation: API usage may require authentication and proper permissions.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph and Click to Edit?

Technical documentation for Click to Edit, API usage, schema components, integration guides, and AI features is available at Hygraph Documentation. For Click to Edit specifics, see Click to Edit setup guide. Limitation: Classic docs are only relevant for Hygraph Classic projects.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. Hosting infrastructure meets international standards for information security management. For more details, visit Hygraph's Secure Features page. Limitation: Additional certifications may be required for certain regulated industries; consult sales for specifics.

Performance & Business Impact

What performance improvements does Hygraph offer?

Hygraph has optimized high-performance endpoints for low latency and high read-throughput content delivery. The read-only cache endpoint provides 3-5x latency improvement. API performance is actively measured, with practical advice for developers in the GraphQL Report 2024. Limitation: Performance may vary based on project complexity and integration setup.

What business impact can customers expect from using Hygraph?

Customers have achieved 3X faster time-to-market (Komax), 15% improved customer engagement (Samsung), and 20% increase in website monetization (AutoWeb). Hygraph supports scaling multilingual content across 12 countries and 10 languages (Voi). Limitation: Results may vary based on project scope and implementation. See case studies.

Use Cases & Customer Proof

Who can benefit from using Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies. Industries represented include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Limitation: Detailed limitations not publicly documented; ask sales for specifics. See industry case studies.

Can you share specific case studies or success stories of customers using Hygraph?

Yes. Samsung improved customer engagement by 15%, Komax achieved 3X faster time-to-market, AutoWeb saw a 20% increase in website monetization, Voi scaled multilingual content across 12 countries and 10 languages, and HolidayCheck reduced developer bottlenecks. For more, visit Hygraph's case studies page. Limitation: Individual results depend on project specifics.

Implementation & Onboarding

How long does it take to implement Hygraph and Click to Edit?

Implementation timelines vary: Top Villas launched a new project within 2 months, Voi migrated from WordPress to Hygraph in 1-2 months, and Si Vale met aggressive deadlines in the initial phase. Onboarding is supported by structured calls, account provisioning, technical kickoffs, documentation, starter projects, and community Slack. Limitation: Complex projects may require longer timelines. See onboarding guide.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Sigurður G. (CTO) noted the UI is intuitive for normal people, Anastasija S. (Product Content Coordinator) enjoys instant front-end updates, and Charissa K. (Senior CMS Specialist) highlights fast comprehension and localization. Limitation: Some advanced features may require technical expertise. See user reviews.

Pain Points & Problems Solved

What problems does Hygraph solve for its customers?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Limitation: Not all pain points may be fully addressed for every use case; consult sales for specifics.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Hygraph
Docs

#Click to Edit setup

Click to Edit lets editors jump from any tagged element in a content preview directly to that field in Hygraph Studio. You configure it on the frontend using the Hygraph Preview SDK. Editors perform the following steps without any further developer involvement:

  1. Hover over a tagged element in preview to display an Edit button.
  2. Click the Edit button to open the corresponding field entry in Studio.
  3. Save changes to automatically refresh the preview.
Click to Edit in content preview

#How it works

The SDK operates in two modes that are automatically detected:

  • Iframe Mode: When your preview loads in an iframe inside Hygraph Studio.
  • Standalone Mode: When your preview loads in a separate browser tab outside Studio.

In both modes, the SDK scans your rendered HTML for data-hygraph-* attributes. These attributes map each element back to a specific entry and field in Hygraph. The SDK adds hover overlays and Edit buttons automatically. When an editor saves in Studio, Hygraph sends a save event to the preview so it can refresh while preserving scroll position.

Real-time field updates are disabled by default. The preview refreshes on save only. You can enable live updates with sync={{ fieldUpdate: true }}.

#Get started

#Availability

  • The Click to Edit feature is available for all projects and is currently in Beta.

#Prerequisites

  • A Hygraph project with at least one model and content entry.
  • A running preview application (local or deployed) using React, Next.js, Remix, Vue, or vanilla JavaScript.

#Setup steps

  1. Install the Preview SDK.
  2. Create a PreviewWrapper component to enable the preview functionality.
  3. Set environment variables.
  4. Add data attributes to content elements.
  5. Set up the Preview widget in Studio.
  6. Verify the setup.

#Install the Preview SDK

The SDK connects your frontend to Studio. It handles overlay rendering, save event listening, and iframe/standalone mode detection.

npm install @hygraph/preview-sdk

#Create the PreviewWrapper component

The PreviewWrapper component initializes the SDK across your application, and enables the preview functionality. Choose the implementation that matches your framework:

#Configuration properties

PropertyRequiredDescription
endpointRequiredYour Hygraph Content API endpoint. See Content API.
studioUrlRequiredYour Studio base URL. Must not end with /. Click to Edit fails in standalone mode if it does.
onSaveOptionalCallback fired after Studio reports a save. Receives the saved entry ID. Use this to trigger revalidation or a router refresh.
debugOptionalEnables verbose console logging. Useful for diagnosing missing attribute issues.
modeOptionalForces 'iframe', 'standalone', or 'auto'. Auto-detection works for most cases.
overlayOptionalCustomize overlay border color, border width, button background, and button text color.
sync.fieldFocusOptionalSynchronizes field focus between Studio and the preview when an editor selects a field.
sync.fieldUpdateOptionalApplies live field changes to the preview as the editor types. Defaults to false.
allowedOriginsOptionalAdditional domains that can host the preview iframe, such as staging or QA environments.

#Set environment variables

Set the following values in .env.local. If you already configured these for live preview, skip this step.

NEXT_PUBLIC_HYGRAPH_ENDPOINT=https://your-region.cdn.hygraph.com/content/your-project-id/master
NEXT_PUBLIC_HYGRAPH_STUDIO_URL=https://your-region.hygraph.com
HYGRAPH_TOKEN=your-permanent-auth-token
  • Content API endpoint: Copy your Content API endpoint from your Hygraph project settings under Project Settings > Access > Endpoints > High Performance Content API. For more information, see our dedicated docs on the Content API.
  • Hygraph Studio base URL: Copy the base Studio URL from your browser's address bar. Example: https://studio-eu-central-1-shared-euc1-02.hygraph.com. Ensure that the URL does not end with a /. Otherwise, Click to Edit will not work in standalone mode, outside of Hygraph Studio.
  • Permanent Auth Token: You can create a Permanent Auth Token under Project Settings > Access > Permanent Auth Tokens. Check that the default content stage is DRAFT. For more information, see our dedicated docs on Permanent Auth Tokens.
    • This is needed only if your Hygraph project requires authentication for Content API requests.

#Add data attributes to content elements

The SDK uses data-hygraph-* attributes to map rendered elements back to Hygraph fields. Add them to the JSX or HTML elements that render Hygraph content. You do not need to instrument every element; add attributes only to the fields editors need to edit from the preview.

The SDK scans rendered HTML for these attributes and attaches hover overlays and Edit buttons automatically.

AttributeRequiredDescription
data-hygraph-entry-idRequiredThe content entry ID. Every editable element needs this. Always use the root entry ID, not a component instance ID.
data-hygraph-field-api-idOptionalThe API ID of the field in the schema. Without this, clicking Edit opens the entry without focusing a specific field.
data-hygraph-rich-text-formatOptionalFormat for Rich Text fields. Accepts html, markdown, or text.
data-hygraph-component-chainOptionalJSON array describing the path to a nested component field. See tagging component fields.

data-hygraph-entry-id - Content entrydata-hygraph-entry-id - Content entry

To find the data-hygraph-field-api-id:

  1. Open Schema and select your model.
  2. Locate the field. The API ID appears next to the field name in camelCase without any spaces.
  3. Use that value as data-hygraph-field-api-id.

data-hygraph-field-api-id - Schemadata-hygraph-field-api-id - Schema

#Tagging component fields

Components require the data-hygraph-component-chain attribute in addition to the standard attributes. This tells Studio how to navigate from the root entry to the specific nested component instance.

The chain is a JSON array of { fieldApiId, instanceId } objects ordered from outermost to innermost component. The instanceId is the unique identifier of the component instance returned in your GraphQL response. It is not the component type's API ID, and it does not appear in the Studio UI.

AttributeDescription
data-hygraph-entry-idThe root content entry ID. Never use a component's own ID here.
data-hygraph-field-api-idThe API ID of the specific field inside the component. Identifies which field to focus within the entry in the editor. Without it, the edit button opens the entry unfocused.
data-hygraph-component-chainJSON array of { fieldApiId, instanceId } describing the path from root entry to the target field.
  • fieldApiId - The field that contains the nested component.
  • instanceId - Unique identifier of the component instance, as returned in your GraphQL query as described below. This is not the API ID of the component.

Data attributes components markupData attributes components markup

#Query to retrieve instanceId

Retrieve the instanceId using the following query:

#Set up the Preview widget in Studio

If you have already configured a Preview widget for live preview, you can skip this step. Click to Edit uses the same widget.

  1. Open your Hygraph project.
  2. Navigate to Schema and select your model.
  3. Click the Sidebar tab.
  4. Select the Preview widget from the right sidebar.
  5. Complete the Preview name and the URL template fields, and click Add.

#Verify the setup

After completing all setup steps, confirm Click to Edit is working end to end.

  1. Open an entry in Studio for the model you configured live preview.
  2. In the right sidebar, under Preview, click Open live preview. The preview should load alongside the entry form.
  3. Hover over an element you tagged with data-hygraph-* attributes. An Edit button should appear.
  4. Click Edit. Studio should scroll to and focus the corresponding field in the entry form.
  5. Edit the field value and click Save & Preview. The preview should refresh and show the updated content.

If the Edit button does not appear at step 3, add debug={true} to your PreviewWrapper component and check the browser console for attribute warnings. Common causes are listed in Troubleshooting below.

#Known limitation

Click to Edit cannot navigate to a field in a specific locale. The Edit button opens the correct field in the default locale, but the editor needs to select the field for the target locale manually within Studio.

Click to Edit - Localized fields

#Troubleshooting

#Edit buttons do not appear

  • Confirm data-hygraph-entry-id is present on the element.
  • Add debug={true} to your PreviewWrapper component and check the browser console.
  • Verify NEXT_PUBLIC_HYGRAPH_ENDPOINT is set correctly.

#Preview does not open

Vercel sets an X-Frame-Options response header that blocks iframe loading. In your Vercel project, go to Settings > Deployment Protection and disable Vercel Authentication.

#Preview does not refresh after saving

  • Confirm the onSave callback calls your framework's refresh method, for example, router.refresh() in Next.js.
  • Verify your Permanent Auth Token has DRAFT set as the default content stage.
  • Confirm your GraphQL queries request the DRAFT stage in preview mode.

#Real-time field updates not working

Real-time updates are disabled by default. Add sync={{ fieldUpdate: true }} to your PreviewWrapper component to enable them.

#Components do not focus correctly

  • Check that data-hygraph-entry-id is always the root entry ID, not the component instance ID.
  • Verify the instanceId values in your component chain match the id fields returned by your GraphQL query.
  • Confirm the component chain array is ordered from outermost to innermost component.

#What's next