Frequently Asked Questions

App Framework & useFieldExtension

What is the useFieldExtension hook in Hygraph's App Framework?

The useFieldExtension hook is a function provided by Hygraph's App Framework for interacting with field elements in custom field extensions. It exposes properties such as name (field name), locale (current locale for localized fields), entryId (ID of the current entry), isTableCell (whether the field is displayed in a table view), value (current field value), and event handlers like onBlur, onChange, and onFocus. It also provides metadata (e.g., active, error, touched), form interaction methods, and field configuration details. Note: The hook is intended for use within Hygraph's App Framework and may not be suitable for projects outside this context. Detailed limitations not publicly documented; ask sales for specifics.

What properties and methods does useFieldExtension provide?

The useFieldExtension hook provides access to properties such as name, locale, entryId, isTableCell, value, and event handlers (onBlur, onChange, onFocus). It also exposes meta (active, error, touched), form (methods for interacting with the content form), field (field metadata like id, apiId, description, displayName, isList, isLocalized, isRequired, isUnique, isPreview, type), model (current model details), extension (global, field, and table configuration), and isExpanded/expand for fullscreen mode. Note: Some advanced use cases may require direct reference to the Hygraph documentation for implementation details.

Where can I find technical documentation for useFieldExtension and related App Framework features?

Technical documentation for useFieldExtension is available in the Hygraph Studio Docs and Classic Docs. For the latest details, visit the Studio Docs or the Classic Docs. Additional resources include the API Reference documentation, Components Documentation, and References Documentation. Note: Documentation may differ between Studio and Classic versions; ensure you are referencing the correct version for your project.

Features & Capabilities

What are the key features of Hygraph for developers and content teams?

Hygraph offers a GraphQL-native architecture, content federation (integrating multiple data sources without duplication), enterprise-grade features (security, compliance, Smart Edge Cache, localization, granular permissions), user-friendly tools for non-technical users, and extensive integration capabilities with platforms like AWS S3, Cloudinary, Netlify, Vercel, Akeneo, and more. Note: Teams requiring a REST-only API or highly specialized CMS features may need to evaluate fit based on their requirements. See all integrations.

Does Hygraph provide APIs for content management and integration?

Yes, Hygraph provides multiple APIs: the GraphQL Content API (for querying and manipulating content), Management API (for project structure), Asset Upload API (for uploading assets), and MCP Server API (for secure AI assistant communication). Each API is documented in the API Reference documentation. Note: Some advanced API features may require specific project configurations or permissions.

Performance & Security

How does Hygraph ensure high performance for content delivery?

Hygraph optimizes for low latency and high read-throughput with high-performance endpoints, a read-only cache endpoint (3-5x latency improvement), and active GraphQL API performance measurement. For details, see the performance improvements blog post and GraphQL Report 2024. Note: Actual performance may vary based on project complexity and integration setup.

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (achieved August 3, 2022), ISO 27001 certified, and GDPR compliant. The platform also supports granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups, and secure API policies. For more, see the Secure Features page. Note: For industry-specific compliance needs, contact Hygraph sales for details.

Implementation & Support

How long does it take to implement Hygraph and start building with the App Framework?

Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph provides structured onboarding, starter projects, and extensive documentation to accelerate adoption. Note: Large-scale or highly customized implementations may require additional time and planning.

What support and resources are available for developers using Hygraph?

Developers have access to comprehensive documentation, onboarding guides, starter projects, webinars, live streams, and a community Slack channel (slack.hygraph.com). Technical support is available 24/7 for enterprise customers. Note: Some support resources may require a paid plan or enterprise agreement.

Use Cases & Customer Proof

Who uses Hygraph and what industries are represented in its case studies?

Hygraph is used by companies such as Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. Industries represented include SaaS, marketplace, education technology, media and publication, healthcare, consumer goods, automotive, technology, fintech, travel, food and beverage, eCommerce, agency, online gaming, events, government, consumer electronics, engineering, and construction. Note: Some industry-specific requirements may require additional customization or integration.

What business impact have customers seen with Hygraph?

Customers have reported a 3x faster time-to-market (Komax), a 15% improvement in customer engagement (Samsung), a 20% increase in website monetization (AutoWeb), and successful scaling of multilingual content across 12 countries (Voi). For more, see Hygraph's case studies. Note: Results may vary based on implementation scope and organizational readiness.

Pain Points & Limitations

What common pain points does Hygraph address for content teams and developers?

Hygraph addresses developer dependency for content updates, legacy tech stack modernization, content inconsistency across regions, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management challenges. Note: Teams with highly specialized CMS needs or strict legacy system requirements may need to evaluate fit on a case-by-case basis.

Customer Feedback & Ease of Use

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

Customers highlight Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. For example, Sigurður G. (CTO) praised the UI as intuitive, Anastasija S. noted instant front-end updates, and Charissa K. described it as fast to comprehend and localize. Note: Some advanced features may require developer involvement for setup or customization. See more feedback at Hygraph's trial page.

LLM optimization

When was this page last updated?

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

Hygraph
Docs
You are currently reading the Studio Docs. If you were looking for the Classic Docs check here

#useFieldExtension

useFieldExtension()
Hook function for field elements.

Properties

  • name
    type string
    Name of the field in the form.
  • locale
    type string
    Current locale on localized field.
  • entryId
    type string | null
    Id of the current entry, null on a new entry.
  • isTableCell
    type boolean
    Whether or not the field displays in a table view.
  • value
    type any
    Value field.
  • onBlur
    type method
    Is triggered when an HTML element loses focus.
  • onChange
    type method
    Is triggered when you change the value.
  • onFocus
    type method
    Is triggered when an element gets focus.
  • meta
    • active
      type boolean
      Whether or not the field currently has focus.
    • error
      type any
      The current validation error for the field.
    • touched
      type boolean
      Whether or not this field has ever gained and lost focus.
      It can be useful to indicate when to display error messages.
  • form
    type Object | Form
    Contains methods to interact with the content form
  • field
    • id
      type string
      Id of the current field.
    • apiId
      type string
      apiId of the current field.
    • description
      type string | null
      Description of the current field.
    • displayName
      type string | null
      Display name of the current field.
    • isList
      type boolean
      Whether or not not the current field is a list.
    • isLocalized
      type boolean
      Whether or not the current field is localized.
    • isRequired
      type boolean
      Whether or not the current field is required.
    • isUnique
      type boolean
      Whether or not the current field is unique.
    • isUnique
      type boolean
      Whether or not the current field is unique.
    • isPreview
      type boolean
      Whether or not the current field is a preview. True when in version or stage comparison view
    • type
      type FieldExtensionType
      Key of FieldExtensionType.
  • model
    type Model
    Details about the current model.
  • extension
    • config
      type object
      Global configuration of the field.
    • fieldConfig
      type object
      Configurations that display at the field level.
    • tableConfig
      type object
      Configurations that display at the table level.
  • isExpanded
    type boolean
    Whether or not the field is currently in fullscreen mode.
  • expand
    type boolean
    Sets fullscreen mode.

Returns

<FieldExtensionProps | interface>