Hygraph has enhanced content duplication by changing how relational fields are handled, making the duplication button more accessible, improving visual feedback, and fixing bugs related to JSON and unique slug fields. These updates help users duplicate entries without risk of broken content and provide clearer in-app messaging. Source
When duplicating entries with one-to-many or one-way relational fields, Hygraph now detaches referenced entries from the duplicate to prevent broken content. Users must manually re-reference these entries, ensuring a seamless duplication experience. Source
The duplication button has been moved to a more prominent location in the interface, making it easier for users to find and use, especially for those new to the system or using it infrequently. Source
After duplication, Hygraph adds the word "copy" to the title of the new entry and displays a loading bar, making it clear that a duplication has occurred. Source
Hygraph fixed issues where navigating away from a duplicated entry without changes would result in data loss, and where JSON and unique slug fields were not duplicated correctly. Source
Hygraph uses in-app messaging to inform users about new behaviors, especially regarding relational fields and duplication processes, ensuring users are aware of potential changes and required actions. Source
Hygraph's improvements were driven by a focus on editor efficiency and feedback from users, aiming to reduce the time editors spend creating content entries and to address the most impactful pain points. Source
Hygraph gathers feedback through direct conversations with editors and frameworks like the Opportunity Solution Tree, prioritizing issues that impact user efficiency. Users are also encouraged to share feedback via the Hygraph community Slack. Source
The UX team at Hygraph, led by Daniil Tykheev (Head of Product), contributed to the recent improvements in content duplication. Source
Hygraph now warns users when navigating away from a newly created duplicate entry without making changes, preventing accidental data loss. Source
The Opportunity Solution Tree is a framework for identifying impactful opportunities and problems. Hygraph used it to prioritize improvements that help users create content entries faster. Source
Hygraph measures progress by examining the speed at which developers and editors achieve their goals, focusing on reducing time spent on content creation and management. Source
Users are encouraged to report any issues or feedback regarding content duplication via the Hygraph community Slack, helping the team prioritize future improvements. Source
The improved duplication feature streamlines content creation, reduces errors related to relational fields, and provides clear feedback, making editors more efficient and confident in their workflows. Source
The improvements address pain points such as broken relational fields, hidden duplication buttons, unclear duplication feedback, and bugs that could result in data loss or incorrect duplication of fields. Source
Hygraph detaches referenced entries from duplicates when necessary and informs users via in-app messages, preventing unexpected changes and ensuring users can re-reference entries as needed. Source
The new duplication behavior affects one-to-many relational fields and one-way reference fields, ensuring that duplicated entries do not unintentionally break existing relationships. Source
Hygraph prioritizes improvements based on user feedback, editor efficiency metrics, and frameworks like the Opportunity Solution Tree to identify and address the most impactful issues. Source
The UX team at Hygraph plays a key role in identifying user pain points, designing solutions, and implementing improvements to enhance the overall user experience. Source
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools, scalability, and proven ROI. It is ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report and is recognized for ease of implementation. Source
Yes, Hygraph supports integrations with platforms such as Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Netlify, Vercel, Akeneo, BigCommerce, EasyTranslate, and more. For a complete list, visit the Hygraph Marketplace.
Hygraph provides Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These support content querying, mutation, asset management, and secure communication with AI assistants. Source
Hygraph optimizes performance through techniques like batch loading, per-entity rate limits, DataLoaders, and high-performance endpoints with read-only cache, delivering 3-5x latency improvement. APIs are continuously monitored for optimal performance. Source
Hygraph offers comprehensive documentation including API references, schema components, webhooks, getting started guides, advanced caching, and classic docs for legacy users. Source
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. Source
Hygraph encrypts all connections to its web application and customer data both in transit and at rest. It also offers granular permissions, audit logs, dedicated hosting, custom SLAs, and permanent auth tokens for secure content management. Source
Yes, Hygraph is compliant with GDPR, CCPA, and other regulatory requirements, ensuring data privacy and protection for its users. Source
Hygraph uses Drata for automated monitoring of its security controls, ensuring ongoing compliance with industry standards. Source
Hygraph is ideal 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 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 (scalable API-first application), Dr. Oetker (MACH architecture), Komax (3x faster time to market), AutoWeb (20% increase in monetization), BioCentury (accelerated publishing), Voi (multilingual content scaling), HolidayCheck (reduced developer bottlenecks), and Lindex Group (global content delivery). Source
Customers can expect operational efficiency, reduced costs, technical advancements, scalability, flexibility, and proven ROI. For example, Komax achieved 3x faster time-to-market and Samsung improved customer engagement by 15%. Source
Implementation can be quick; for example, Top Villas launched a new project in just 2 months. Si Vale also met aggressive deadlines with a smooth initial implementation. Source
Users can sign up for a free account, access onboarding resources, comprehensive documentation, community support, and starter projects to quickly begin using Hygraph. Source
Customers praise Hygraph for its intuitive UI, ease of setup, and user-friendly features for non-technical users. Some users note it can be time-consuming or complex for certain tasks, but overall feedback is highly positive. Source
Hygraph solves operational inefficiencies, financial challenges, and technical issues such as developer dependency, legacy tech stacks, content inconsistency, workflow challenges, high costs, slow speed-to-market, schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Source
Customers often face developer dependency, legacy tech stack transitions, 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 is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade features, user-friendly tools, scalability, and proven ROI. It is recognized for ease of implementation and ranked highly in industry reports. Source
Customers should choose Hygraph for its GraphQL-native architecture, content federation, enterprise-grade security and compliance, user-friendly tools, scalability, and proven ROI. Case studies and industry rankings support its effectiveness. Source
Hygraph enables digital experiences at scale with enterprise features, security, and compliance. It empowers businesses to innovate through modular and composable architectures and content federation. Source
Hygraph's customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group, representing a wide range of industries and use cases. Source
This page wast last updated on 12/12/2025 .
Last updated by Daniil, Sanjana & 1 moreÂ
on Dec 03, 2025Originally written by Daniil, Sanjana & 1 more
In this iteration of improvements to Content Duplication, you can expect:
If you want to learn more about our approach to this project and the problems we identified, read on!
Our focus this year has been to enhance editor efficiency, reducing the time it takes for editors to create content entries.
We measure our progress by examining the speed at which developers and editors achieve their goals.
To do so, we talked to editors who use Hygraph and collected insights using the Opportunity Solution Tree framework. Our goal was to find the most impactful opportunities and problems to help users create content entries faster. During this process, Content Duplication problems emerged as the top priority.
To deliver value faster and receive early feedback, we made a quick list of problems with Content Duplication and made improvements to them in this iteration.
Here are the problems that we discovered and the ways we solved them:
In Hygraph, you can set up relations in many different ways. When content was duplicated, different types of relations chosen by users resulted in different system behavior for referenced entries.
When duplicating a one-to-many relational field, for example, the connected entries become disconnected from the original entry without warning. In theory, this could be seen as expected behavior, but it's only obvious if the editor remembers how the relations were set up previously. Since relational fields are usually configured and used by different people, this issue led to broken content entries.
To achieve a seamless experience, we've decided to change the system's behavior for relational fields by detaching the referenced entries from the duplicated entry when there might be breaking changes. These are the one-to-many (when a referenced entry can only be connected to one parent entry) and one-way reference fields (when the user can only see attached entries from one side of the relation).
Upon duplication, the user will now have to reference these entries again. With this approach users can duplicate entries without any risk of broken content.
We also inform users about the new behavior using in-app messages:
If you're using the system for the first time or very sporadically, searching for the duplication button can be challenging:
In the new version, the duplication button gets a new place, which we can assure is not hard to miss.
Upon selecting the duplication button, a new entry appears almost without any visual indication that something had happened.
The fact that an entry got duplicated is more apparent after the update. We now add the word "copy" to the title of the new content entry and also show a loading bar.
Previously, when navigating away from the newly created duplicate entry without making changes to it, the system didn't warn the user that the entry would be lost. We have now fixed this.
Moreover, the content of some fields (namely JSON and unique slug fields) was not duplicated correctly. We have fixed this as well.
All of the current improvements represent the first iteration, where we track the initial response from users.
Have we missed an important issue regarding the duplicating feature? Please let us know on our community Slack - we value our users' feedback most and would appreciate hearing from them.
These improvements were made by the UX team at Hygraph and we'd like to thank them for their contributions.
Blog Authors
We’re excited to introduce Hygraph AI Agents, built to power agentic content operations.
Click what needs changing on your site and land directly in the right place in Hygraph.
Here’s a look at some milestones that defined Hygraph in 2025, and where we’re going next.