To duplicate a content entry in Hygraph, navigate to the content editor, select the entry you want to duplicate, and click the duplicate icon at the top of the screen. The duplicated entry will load with '(copy)' appended to the title. You can then make changes and save or publish the entry as needed. Learn more.
When you duplicate a content entry, Hygraph automatically adds '(copy)' to the end of fields marked as Title in the schema, making it easy to distinguish the duplicated entry from the original. More info.
When duplicating a content entry, Hygraph duplicates the reference (the link between entries), but not the referenced entry itself. The system notifies you if some relations are not duplicated, depending on the reference configuration. Details here.
Hygraph's behavior depends on the reference configuration. For example, one-way references to one or many are duplicated, while two-way one-to-one references are not duplicated and must be added manually. The system provides a table outlining behaviors for various configurations. See the table.
Hygraph does not duplicate references with one-to-one cardinality. You will need to add these references manually after duplication. Learn more.
To duplicate related content, navigate to the content entry with the relation, use the context menu to select 'Duplicate', edit as needed, and save. The duplicated reference will appear in the reference field. Full instructions.
If the field allows referencing only one model, the duplicate will replace the original reference in the content entry. Details here.
If the field allows referencing more than one model, the duplicate will display as an additional reference in the content entry. Learn more.
Yes, if you attempt to leave a duplicated entry without saving, Hygraph will warn you to prevent accidental data loss. More info.
You can find detailed documentation on field configuration, including how to set fields as titles and manage references, in the Hygraph docs: Field configuration documentation.
Duplicating related content allows you to keep the format of the original while making edits that won't affect other entries using the same reference, streamlining content management and reducing errors. Learn more.
Yes, you can duplicate content in both Studio and Classic versions. For Classic Docs, refer to Classic documentation.
No, duplicating a content entry creates a new entry with the same content, leaving the original entry unchanged. You can then edit the duplicated entry independently. Details here.
The word '(copy)' is appended to the title field of duplicated entries, making it easy to identify them in the content editor. More info.
Yes, after duplicating an entry, you can make any necessary changes before saving or publishing it, allowing you to customize the new entry as needed. Learn more.
If a reference is not duplicated automatically (e.g., in two-way one-to-one configurations), you can manually add the reference to the duplicated entry. The system will notify you when this is required. Details here.
Yes, Hygraph will notify you if certain references are not duplicated due to their configuration, so you can take manual action if needed. More info.
Yes, you can duplicate entries with complex reference structures, but some references may require manual adjustment depending on their configuration. The system provides guidance during the duplication process. Learn more.
Using the duplicate feature in Hygraph allows you to quickly create new entries based on existing ones, maintaining consistency in structure and content while allowing for easy customization. More info.
Duplicating content streamlines workflows by enabling editors to quickly create variations or new versions of existing content, reducing manual effort and ensuring consistency across entries. Learn more about content workflows.
Hygraph offers a GraphQL-native architecture, content federation, enterprise-grade security and compliance, Smart Edge Cache, localization, granular permissions, and a user-friendly interface for both technical and non-technical users. Source.
Yes, Hygraph supports content federation, allowing you to integrate multiple data sources without duplication and deliver consistent content across channels. Learn more.
Hygraph offers integrations with digital asset management systems (e.g., Aprimo, AWS S3, Bynder, Cloudinary), hosting platforms (Netlify, Vercel), commerce and PIM (Akeneo, BigCommerce), translation tools (EasyTranslate), and more. See the full list at the Hygraph Marketplace.
Yes, Hygraph provides several APIs, including Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These support querying, mutating, uploading, and managing content. API Reference.
Hygraph offers comprehensive technical documentation, including API references, schema guides, webhooks, getting started guides, advanced caching, and classic docs for legacy users. Documentation.
Hygraph measures GraphQL API performance and provides optimization techniques such as batch loading, per-entity rate limits, and DataLoaders. High-performance endpoints with read-only cache deliver 3-5x latency improvement. Performance details.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure high standards for security and data protection. Security features.
Hygraph encrypts all connections, ensures data is encrypted in transit and at rest, offers granular permissions, audit logs, dedicated hosting, and continuous monitoring via Drata. More on security.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, Smart Edge Cache, localization, and is recognized for ease of implementation and robust security. Case studies.
Hygraph is ideal for developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses in industries such as eCommerce, SaaS, media, healthcare, automotive, and more. Industries served.
Customers report operational efficiency, reduced costs, faster launches, improved scalability, and proven ROI. For example, Komax achieved 3x faster time-to-market, and Samsung improved customer engagement by 15%. See case studies.
Hygraph eliminates developer dependency, modernizes legacy tech stacks, ensures content consistency, streamlines workflows, reduces costs, accelerates speed-to-market, and simplifies integration and localization. Learn more.
Hygraph addresses operational inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization challenges. Source.
Industries 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. See all industries.
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), and Voi (multilingual content at scale). Read case studies.
Hygraph is quick to implement, with some customers launching in as little as 2 months. Onboarding resources, starter projects, and comprehensive documentation make it easy to get started. Getting started guide.
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 enables digital experiences at scale with enterprise features, security, and compliance. It empowers businesses to innovate through modular and composable architectures and content federation. Learn more.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, robust security, and is recognized for ease of implementation. It is suitable for developers, content creators, enterprises, and agencies, with proven ROI and market recognition. Comparison details.
Hygraph stands out for its GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, and proven customer success. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. See why.
Developers benefit from GraphQL-native APIs and schema evolution; content creators enjoy an intuitive UI; enterprises gain robust security and scalability; agencies can efficiently manage multiple projects. Details here.
Implementation can be as quick as 2 months, as demonstrated by Top Villas. Onboarding resources and starter projects help accelerate adoption. Implementation example.
Hygraph provides onboarding guides, technical documentation, community Slack, and starter projects to help new users get started quickly. Getting started.
Starter projects with pre-configured schemas and models are available on the Hygraph Marketplace Starters page to help you jumpstart your development.
Hygraph offers high-performance endpoints, including a read-only cache endpoint that delivers 3-5x latency improvement, and continuously monitors and optimizes API performance. Performance blog.
Hygraph recommends batch loading, per-entity rate limits, and DataLoaders to enhance API efficiency and performance. API optimization tips.
This page wast last updated on 12/12/2025 .
Inside each content entry, editors have the option to duplicate content.
Follow these steps to duplicate content:
Save or Save & publish depending on your workflow. If you try to leave without saving, the system will warn you.The system adds the word (copy) at the end of fields marked as Title in the schema.
Use as title field - Schema field configuration
Check out our Field configuration document for more information about this.
Note that if the content entry contains reference fields, some of the relations will be duplicated and others won't. The system will notify you if this is the case:
References not duplicated
What is copied in this case is the reference - the link between the two content pieces - but not the referenced entry itself.
The following table explains the system behavior depending on reference configuration:
| Type | Direction | Cardinality | System behavior |
|---|---|---|---|
| Can reference only one model | One-way reference | To one | The system duplicates the reference. |
| Can reference only one model | Two-way reference | One to one | The system does not duplicate the reference. You can add it manually. |
| Can reference only one model | One-way reference | To many | The system duplicates the reference. |
| Can reference only one model | Two-way reference | Many to many | The system duplicates the reference. |
| Can reference multiple models | Two-way reference | One to one | The system does not duplicate the reference. You can add it manually. |
| Can reference multiple models | Two-way reference | Many to many | The system duplicates the reference. |
| Can reference multiple models | Two-way reference | Many to one | The system duplicates the reference. |
The system will not duplicate references with the cardinality one to one.
When viewing content that has relations (references), you can quickly duplicate referenced entries within an original entry. This is a quick way to keep the format of the related content, while allowing you to make content edits that won't affect other entries that contain the same reference.
Duplicating related content
Navigate to the content entry that contains the relation you want to duplicate.
Click on the context menu and select Duplicate.
The duplicated reference screen will display. Here you can make the necessary edits, then click Save or Save & Publish depending on your workflow.
Click on the X at the top-left corner of the editor to return to the original content entry you were working on. The reference field now contains the duplicated reference.
System behavior depends on field configuration:
If the field allows referencing only one model, the duplicate will replace the original.
If the field allows referencing more than one model, the duplicate will display as an additional reference.
Inside each content entry, editors have the option to duplicate content.
Follow these steps to duplicate content:
Save or Save & publish depending on your workflow. If you try to leave without saving, the system will warn you.The system adds the word (copy) at the end of fields marked as Title in the schema.
Use as title field - Schema field configuration
Check out our Field configuration document for more information about this.
Note that if the content entry contains reference fields, some of the relations will be duplicated and others won't. The system will notify you if this is the case:
References not duplicated
What is copied in this case is the reference - the link between the two content pieces - but not the referenced entry itself.
The following table explains the system behavior depending on reference configuration:
| Type | Direction | Cardinality | System behavior |
|---|---|---|---|
| Can reference only one model | One-way reference | To one | The system duplicates the reference. |
| Can reference only one model | Two-way reference | One to one | The system does not duplicate the reference. You can add it manually. |
| Can reference only one model | One-way reference | To many | The system duplicates the reference. |
| Can reference only one model | Two-way reference | Many to many | The system duplicates the reference. |
| Can reference multiple models | Two-way reference | One to one | The system does not duplicate the reference. You can add it manually. |
| Can reference multiple models | Two-way reference | Many to many | The system duplicates the reference. |
| Can reference multiple models | Two-way reference | Many to one | The system duplicates the reference. |
The system will not duplicate references with the cardinality one to one.
When viewing content that has relations (references), you can quickly duplicate referenced entries within an original entry. This is a quick way to keep the format of the related content, while allowing you to make content edits that won't affect other entries that contain the same reference.
Duplicating related content
Navigate to the content entry that contains the relation you want to duplicate.
Click on the context menu and select Duplicate.
The duplicated reference screen will display. Here you can make the necessary edits, then click Save or Save & Publish depending on your workflow.
Click on the X at the top-left corner of the editor to return to the original content entry you were working on. The reference field now contains the duplicated reference.
System behavior depends on field configuration:
If the field allows referencing only one model, the duplicate will replace the original.
If the field allows referencing more than one model, the duplicate will display as an additional reference.