Phenomenon · phenomenon:electrocaloric-effect

Electrocaloric effect

An applied electric field changes the temperature of a polar dielectric by changing its dipolar entropy. The converse of the pyroelectric effect.

Condensed matterfirst reported 1930

Atlas record: 3 claims reference this phenomenon — 2 replicated and 1 established.

Explorerelations · matrix context · routes · sources · cite

conditions: solid · ferroelectric required · electric field or bias required

3claims1enumerated routes0routes with complete-composition evidence0candidate routes not searched2cited sources

Relations

drives · 1

Changing electric field—drives→Electrocaloric effectreplicated

a large field applied to a thin polar dielectric near its transition

produces · 1

Electrocaloric effect—produces→Temporal temperature changereplicated

member of · 1

Electrocaloric effect—member of→Caloric (magneto/electro/elasto)established

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

D.25 × C.09 · Changing electric field × Caloric (magneto/electro/elasto) · Established

family: Caloric (magneto/electro/elasto) (C.09)

Enumerated routes through this · 1

Changing electric field → Electrocaloric effect → Temporal temperature change → Pyroelectric effect → Separated surface charge → Electrical work5/5 est · same energy form

Cited sources · 2

[1]
A. S. Mischenko et al.. Giant electrocaloric effect in thin-film PbZr0.95Ti0.05O3 (2006)
Science 311, 1270–1271 · doi:10.1126/science.1123811 · crossref ✓ 2026-09-19 · record
[2]
X. Moya, S. Kar-Narayan, N. D. Mathur. Caloric materials near ferroic phase transitions (2014)
Nature Materials 13, 439–450 · doi:10.1038/nmat3951 · crossref ✓ 2026-09-19 · record

Cite this entity

Physical Transformation Atlas (2026). entity phenomenon:electrocaloric-effect: Electrocaloric effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/phenomenon/electrocaloric-effect

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.