Synthetic data

On this page 8

Synthetic data is information that is artificially generated by an algorithm rather than collected from real-world events, designed to reproduce the statistical properties and structure of a source dataset without containing its actual records. As a concept in data fundamentals, it sits between real raw data and pure simulation: a synthetic table looks and behaves like the original, yet no row corresponds to a real customer, patient or transaction.

Organizations use synthetic data to share, test and train models when real data is scarce, sensitive, expensive or legally restricted. Its value depends on a constant balance between fidelity, utility and privacy, and no generation method maximizes all three at once.

How synthetic data is generated

Synthetic data is produced by a generative process that learns or encodes the patterns of a domain and then samples new records from that representation. The process can be fully rule-based, fully learned from a real dataset, or a hybrid of both.

Learned generators first fit a model to the source data, capturing marginal distributions, correlations between columns and, for sequences, temporal dependencies. The generator then samples new records from the fitted model. Rule-based generators skip the fitting step and draw values from distributions and constraints defined by experts, such as valid postal codes or plausible age ranges.

The table below summarizes the main generation families and what they capture well.

MethodHow it worksStrengthWeakness
Rule-based samplingDraws values from hand-defined distributions and constraintsFull control, no privacy exposureMisses real correlations
Statistical modelsFits Bayesian networks or copulas to source dataInterpretable, good for tabular dataStruggles with complex dependencies
Generative adversarial networksA generator competes against a discriminatorRealistic images and mixed tablesUnstable training, mode collapse
Variational autoencodersEncodes data into a latent space and decodes samplesStable training, smooth variationOutputs can be blurred or averaged
Diffusion and language modelsIteratively denoises or predicts tokensHigh fidelity for text, images and sequencesHigh compute cost, memorization risk
Agent-based simulationModels entities and rules that interact over timeCaptures scenarios with no historyRealism depends on model assumptions
Common synthetic data generation methods

Types of synthetic data

Synthetic data is classified by how much real data it contains and by the modality it represents. The degree of synthesis matters most for privacy, because partially synthetic records still carry real values.

TypeReal contentTypical usePrivacy level
Fully syntheticNone; every value is generatedExternal sharing, public test setsHighest
Partially syntheticOnly sensitive columns are replacedInternal analytics with masked fieldsModerate
HybridReal and generated records mixedAugmenting small or imbalanced datasetsVariable
SimulatedNone; derived from physical or behavioral modelsRobotics, autonomous driving, stress testsHighest
Degrees of synthesis and their typical use

By modality, synthetic data covers tabular records, time-series data such as sensor readings, free text, images, video and graphs. Structured data is the most mature area, while unstructured data generation relies mostly on deep generative models.

Fidelity, utility and privacy

The quality of synthetic data is judged on three dimensions that pull against each other. Fidelity measures how closely the synthetic distribution matches the source; utility measures whether analyses or models built on synthetic data reach conclusions similar to those built on real data; privacy measures how little the output reveals about any real individual.

A generator that reproduces the source perfectly is effectively copying the data, which destroys privacy. Adding noise or coarsening patterns protects individuals but erodes utility, especially for rare subgroups and outliers. Practitioners therefore set an acceptable level for each dimension based on the use case.

DimensionTypical metricWhat a poor result signals
FidelityDistribution distance, correlation differencePatterns missing or distorted
UtilityTrain on synthetic, test on real (TSTR) scoreModels fail on real data
PrivacyDistance to closest record, membership inference attacksRecords leak or can be re-identified
CoverageShare of real categories and ranges presentRare cases silently dropped
How synthetic data quality is evaluated

Formal guarantees come from differential privacy, which bounds how much any single source record can influence the generator. A smaller privacy budget, written as epsilon, gives stronger protection but lowers fidelity. Without such a guarantee, synthetic data is not automatically anonymous; overfitted generators can reproduce real rows almost verbatim.

Synthetic data is one of several ways to reduce reliance on sensitive real data, and it is often confused with anonymization and simple data augmentation. The distinctions matter for legal treatment and for what downstream users can safely do.

ApproachWhat changesMain limitation
Synthetic dataAll or part of the records are newly generatedFidelity and privacy must be verified
Anonymization and maskingReal records keep their structure, identifiers removedLinkage attacks can re-identify people
Data augmentationReal samples are transformed, such as rotated imagesCannot create truly new patterns
Aggregated statisticsOnly summaries are releasedNo record-level analysis possible
Open dataReal data published under an open licenseOnly possible for non-sensitive data
Synthetic data versus alternative techniques

Synthetic data also interacts with data lineage and metadata. A synthetic dataset should be clearly labeled as generated, with the source, method, version and privacy parameters recorded, so that no analyst mistakes it for raw data.

Where synthetic data is used

Synthetic data is most valuable where real data cannot move freely or does not exist in sufficient volume. Common applications include the following.

  • Software testing: realistic databases for development and staging environments without exposing production records.
  • Machine learning training: balancing rare classes such as fraud cases or rare diseases, and pretraining on large generated corpora.
  • Data sharing: giving researchers, vendors or partners a dataset that preserves patterns while protecting individuals.
  • Scenario simulation: edge cases for autonomous vehicles, network failures or financial stress tests that are rare or dangerous to collect.
  • Data democratization: letting more teams explore data that would otherwise require restricted access approvals.

Limitations and common mistakes

Synthetic data inherits the flaws of its source and its model. Biased source data yields biased synthetic data, and a generator can even amplify bias by smoothing away minority patterns. Synthetic data also cannot reveal relationships that were never present in the training data.

  • Treating it as automatically anonymous: without privacy testing, memorized records may leak.
  • Validating only marginals: matching each column separately while correlations break down.
  • Ignoring rare subgroups: aggregate metrics look good while small populations are misrepresented.
  • Model collapse: repeatedly training generative models on their own outputs gradually degrades diversity and accuracy.
  • Final decisions on synthetic results alone: high-stakes conclusions should be confirmed on real data where possible.

Good practice is to document the generation process, test fidelity, utility and privacy separately, and treat synthetic data as a complement to real data quality controls, not a replacement for them.

Put simply

Synthetic data is made-up data that behaves like real data. A computer studies a real collection of records, learns its patterns, and then writes brand-new records that follow the same patterns. No row describes a real person.

Think of a skilled forger of handwriting who learns a style but writes entirely new letters. The letters look authentic, yet they say nothing true about the original writer. The catch is that a poor copy misleads, and a perfect copy can expose the original, so the balance has to be checked.

In practice

A regional hospital network wants an outside analytics vendor to build a model that predicts 30-day readmissions, but patient records cannot leave the network. The data team trains a generator on 200,000 historical admissions, including age, diagnosis codes, length of stay and discharge type, using a differentially private method with a moderate privacy budget.

Before release, the team checks that column correlations differ by less than a set tolerance and runs a train on synthetic, test on real comparison internally. A model trained on synthetic records reaches an accuracy score within a few percentage points of one trained on real records, and no synthetic row sits closer to a real patient than a defined distance threshold.

The vendor develops the model on the synthetic dataset, and the hospital then retrains and validates the final version on real data inside its own environment. The outcome is faster collaboration without transferring any patient record.