Rescaling is the CKKS-specific operation that divides a ciphertext by a scaling factor after a homomorphic multiplication to maintain a stable scale and manage noise. It is functionally analogous to truncating the least significant bits of a floating-point number to prevent precision from growing unboundedly. Without rescaling, the scale factor would grow exponentially with each multiplication, quickly exhausting the noise budget and corrupting the ciphertext.
Glossary
Rescaling

What is Rescaling?
Rescaling is the core operation in the CKKS homomorphic encryption scheme that divides a ciphertext by a scaling factor after multiplication to maintain a stable scale and truncate accumulated noise.
This operation reduces the ciphertext modulus proportionally, which also reduces the absolute noise, effectively extending the usable noise budget without executing a costly bootstrapping procedure. Each rescaling consumes one level from the predetermined multiplicative depth, making it a critical resource to track in leveled fully homomorphic encryption. Rescaling is what makes the CKKS scheme uniquely efficient for approximate arithmetic in privacy-preserving machine learning inference.
Key Characteristics of Rescaling
Rescaling is the fundamental CKKS operation that maintains a stable scale and manages noise growth after homomorphic multiplication, analogous to truncating floating-point precision in unencrypted computation.
Core Mechanism
Rescaling divides the ciphertext by a scaling factor (Δ) after multiplication to restore the scale to its original level. In CKKS, a ciphertext encrypts a message m as m · Δ + e, where e is noise. Multiplying two ciphertexts yields a product with scale Δ² and quadratic noise growth. Rescaling divides by Δ, reducing the scale back to Δ and proportionally reducing the absolute noise. This operation consumes one level from the modulus chain, making it a limited resource that must be budgeted during circuit design.
Modulus Chain Management
CKKS operates on a modulus chain—a hierarchy of decreasing moduli q₀ > q₁ > ... > qₗ. Each rescaling operation drops the ciphertext to the next smaller modulus, consuming one level. The initial modulus q₀ determines the multiplicative depth of the computation. A circuit requiring L sequential multiplications needs a modulus chain of at least L levels. Exhausting all levels leaves the ciphertext at the lowest modulus, where no further operations are possible without bootstrapping to refresh the chain.
Fixed-Point Arithmetic Analogy
Rescaling is the encrypted equivalent of fixed-point truncation. In plaintext fixed-point arithmetic, multiplying two k-bit numbers produces a 2k-bit result that must be truncated back to k bits to prevent unbounded growth. Similarly, CKKS multiplication doubles the effective precision, and rescaling truncates it back. This introduces a small approximation error—acceptable because CKKS is designed for approximate arithmetic on real numbers, making it ideal for machine learning workloads where exact integer precision is unnecessary.
Interaction with Relinearization
After multiplication, two operations are typically required: relinearization to reduce ciphertext size, and rescaling to manage scale and noise. The order matters. Rescaling is performed first to bring the scale back to Δ, followed by relinearization to collapse the three-component ciphertext back to two components. Performing relinearization before rescaling would operate on a ciphertext with scale Δ², requiring different key-switching parameters. The standard sequence is:
- Multiply → Rescale → Relinearize
Level Budgeting in Neural Networks
When implementing encrypted inference for neural networks, each homomorphic multiplication (e.g., fully-connected layer, convolution) consumes one level via rescaling. A network with 10 linear layers requires at least 10 levels in the modulus chain. Activation functions like ReLU must be approximated by low-degree polynomials, each multiplication within the polynomial also consuming levels. This forces a trade-off between network depth, polynomial accuracy, and computational cost. Typical CKKS parameters for deep networks use a modulus chain of 16–30 levels.
Rescaling vs. Modulus Switching
While both operations reduce the ciphertext modulus, they serve distinct purposes:
- Rescaling: Divides by the scaling factor Δ after multiplication, maintaining a consistent scale. It is an integral part of CKKS arithmetic.
- Modulus Switching: A general noise management technique that scales down the modulus to reduce absolute noise without a corresponding multiplication. It can be used between operations to extend the noise budget. Rescaling is a specialized form of modulus switching that simultaneously normalizes the scale, making it essential for CKKS's approximate arithmetic model.
Rescaling vs. Modulus Switching vs. Bootstrapping
A comparison of the three primary operations used to control noise growth and manage the modulus chain in leveled homomorphic encryption schemes, with a focus on CKKS.
| Feature | Rescaling | Modulus Switching | Bootstrapping |
|---|---|---|---|
Primary Purpose | Maintain scale invariance after multiplication | Reduce noise magnitude proportionally | Refresh exhausted noise budget to enable unlimited computation |
Operation Type | Division by scaling factor and modulus reduction | Modulus reduction without scale adjustment | Homomorphic evaluation of decryption circuit |
Effect on Noise | Reduces absolute noise proportionally with modulus | Reduces absolute noise proportionally with modulus | Resets noise to a fixed low level |
Effect on Scale | Restores scale to original value | Preserves the current scale | Resets scale to a fresh encoding |
Computational Cost | Low | Low | Very High |
Typical Latency | < 1 ms | < 1 ms | Seconds to minutes |
Supported Schemes | CKKS only | BFV, CKKS | FHE schemes (CKKS, BFV, TFHE) |
Enables Unlimited Computation |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Answers to common questions about the rescaling operation in the CKKS homomorphic encryption scheme, a critical noise management technique for approximate arithmetic.
Rescaling is the CKKS-specific operation that divides a ciphertext by a scaling factor after a homomorphic multiplication to maintain a stable scale and manage noise. In the CKKS scheme, plaintexts are multiplied by a large scaling factor Δ (delta) before encryption to preserve precision during approximate arithmetic. When two ciphertexts are multiplied, the underlying scale becomes Δ², and the noise grows proportionally. Rescaling divides the ciphertext modulus by Δ, effectively truncating the least significant bits—analogous to rounding in floating-point arithmetic—to bring the scale back down to approximately Δ. This operation is essential because it prevents the scale from growing exponentially with each multiplication, which would otherwise cause rapid modulus exhaustion and incorrect decryption. Rescaling is performed using modulus switching, which also reduces the absolute noise in the ciphertext, extending the noise budget for subsequent operations.
Related Terms
Rescaling is a core operation in the CKKS scheme for managing scale and noise. The following concepts are essential for understanding its role in the broader homomorphic encryption lifecycle.
Noise Budget
The finite amount of cryptographic noise a ciphertext can tolerate before decryption becomes corrupted. Each homomorphic operation, especially multiplication, consumes this budget.
- Consumption: Addition consumes noise linearly; multiplication causes it to grow quadratically.
- Management: Rescaling is the primary tool for cutting down noise after multiplication to prevent it from exceeding the total modulus.
- Analogy: Think of the noise budget as the remaining depth capacity of a circuit before the signal is lost.
Leveled Fully Homomorphic Encryption
A variant of HE that supports circuits of a pre-determined multiplicative depth without bootstrapping. Rescaling is the mechanism that enforces this depth limit.
- Parameterization: The initial modulus chain length defines the maximum number of rescalings (and thus multiplications).
- Constraint: The circuit depth must be known at encryption time.
- Advantage: Avoids the massive computational overhead of bootstrapping for shallow circuits, making it the standard mode for many ML inference tasks.
Polynomial Approximation
The technique of replacing non-linear activation functions (ReLU, sigmoid) with low-degree polynomials to enable their evaluation in CKKS. Rescaling is critical here to manage the scale growth from repeated polynomial multiplications.
- Example: Approximating ReLU with a degree-3 polynomial requires 2 multiplications, consuming 2 rescalings.
- Trade-off: Higher-degree approximations improve accuracy but consume more depth.
- Interaction: The choice of polynomial directly impacts the rescaling budget required for a neural network layer.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us