WattPair Appliance Load & Surge Provenance Dataset
32 appliance classes. Running watts, start-up surge, duty cycle and annual energy — and attached to every single figure, the document it was read from, the date it was read, and how much we trust it. Free to reuse under CC BY 4.0.
Read this before you use a number
193 of the
434 figures in this file are
null — 44%. That is not an oversight and it is
not an unfinished import. It is the design: where no manufacturer publishes a figure, the
field stays empty and keeps a status of unknown, because an
estimate dressed as a specification is the failure mode this dataset was built against.
Anyone can produce a wattage chart. Almost nobody publishes which document each row came from, or admits which rows do not exist. That is the part worth downloading.
No sign-up, no email, no rate limit. It is a static file on this domain.
What is in the file
The last row is not a defect list, it is data. Those records carry a
ready_for_page_generation: false and a count of the reasons; they
stay in the file so a reuser can see which classes this project does not consider settled
rather than discovering the gap later. Two engine constant tables ship alongside the records —
surge duration bands and per-load-type power-factor defaults — because a duration in
milliseconds cannot be used correctly without knowing which band it falls into.
Where each start-up figure comes from
Start-up surge is the number that decides whether a machine can be run at all, and it is the number the rest of the web quotes without saying where it got it. Each of the 32 records is labelled with one of four bases.
nameplate_lra 7 Locked-rotor amperage from a compressor or motor data sheet. The strongest evidence in the file: a measured stall current, published by the part’s own manufacturer.
manufacturer_stated 5 A start-up figure the appliance brand published itself, in watts or as a multiple.
category_rule_of_thumb 3 A category envelope this project applied because no figure exists for the class. Labelled as such on every page that uses it, and it is not a manufacturer number.
unknown 17 No start-up figure, and the field is null. For several of these the reason is not that we failed to find one — it is that the category does not publish one at all.
Every field, and what it licenses you to say
Each figure in the file is an object, not a bare number. These are its keys.
value The figure. Null when no source publishes it — never an estimate standing in for one.
unit W, VA, ms, ratio, h, kWh, Wh. Stated per field rather than assumed from the field name.
value_min Lower end of the range, where the class genuinely spans one (model to model).
value_max Upper end of the same range.
display_precision Decimal places this figure supports. A figure read to 1 dp is not a figure known to 3.
source_tier official · measured · user. Everything in this release is official: this project has no laboratory and says so.
source_type What kind of document it was — specification sheet, manual PDF, government standard, support article, product page.
source_url The document itself. This is the field that makes every other one checkable.
verified_date When a human last opened that document and read this figure out of it.
confidence high · medium · low. Low is common and is not an apology — a derived figure or a borrowed coefficient says so here.
status verified · unknown · conflict. A status of conflict means two sources disagree and the disagreement is unresolved, so the figure is not used.
absence_verified The negative record: on this date, these documents were opened and the manufacturer does not publish this figure. Distinguishes “we did not look” from “we looked, it is not there”.
is_derived True when the figure was computed from other published figures rather than read directly (e.g. annual kWh ÷ hours ÷ duty cycle).
Each record also carries a sources array — the documents behind
it, with source_url, source_tier, source_type, covers_fields, verified_date, fetch_status.
Which fields in this record that document backs — so one source cannot silently be credited for the whole record.
What a source tier means
Three tiers exist in this project's schema. Only one of them appears in this release, and that is worth saying plainly rather than leaving to be inferred from the data.
official Read out of a document the manufacturer, a government programme or a standards body published. Every figure in this release is this tier.
measured Measured on a bench by this project. There are none. WattPair has no laboratory, and rather than blur the distinction the tier stays empty until that changes.
user Submitted by a reader who measured it. Held in a review pool; a pairing is only labelled user-verified once three independent logs agree.
official sources
166 Licence and how to credit it
CC BY 4.0. Use it commercially, modify it, build a product on it. The one condition is attribution, and the licence lets us specify the wording — so here it is, ready to copy:
WattPair Appliance Load & Surge Provenance Dataset
© WattPair — CC BY 4.0
Source: https://wattpair.com/data/appliance-load/
The same three lines are embedded inside the JSON, under
dataset.attribution, because people who copy data copy
fields and not documentation. One URL, and it is this page.
A note on what a licence can and cannot do, stated because pretending otherwise would be the dishonest move: under US law facts are not copyrightable, and every figure here is a fact read from a public document. Anyone who retypes these numbers owes us nothing, licence or no licence. Attribution is a social norm, not a lever — we are asking, and most people who write for a living say yes. This is not legal advice.
How it was compiled
Compiled with AI assistance from manufacturer documents, government efficiency filings and standards bodies, then checked against the cited source. Every non-null figure carries the URL it was read from, so any claim here can be re-derived from public documents without trusting this file.
This dataset is deliberately incomplete and says where. Start-up surge data does not exist for several appliance classes — not "we did not find it", but "the manufacturers do not publish it" — and those fields are null with a status of unknown rather than estimated. Read stats.null_fields and stats.surge_basis before using any figure.
What is deliberately not in it
Not published. That library is what this site sells against, and opening it would be giving away the commercial core rather than the research.
Not published — though its thresholds are, in full, on the methodology page. The constants were never the secret; the constraint ordering is.
Where two documents disagree, the field is marked conflict and
the figure is withheld — but the internal queue of unresolved disagreements, with its
quoted excerpts, stays internal.
test_conditions — coming in v0.2.0
Per-field test conditions (what was measured, under what load, at what voltage). Recorded for every non-null figure, in Chinese. English translation is stage P-A.
source_label — coming in v0.2.0
Human-readable label for each source document. The machine-readable source_url, source_type and source_tier are exported now.
short_description — coming in v0.2.0
One-paragraph description of each appliance class.
blocking_reasons — coming in v0.2.0
Why a record is not yet cleared for page generation. The boolean ready_for_page_generation is exported now, and so is the count of reasons.
Those last rows are the honest version of a gap. The research behind this dataset was written in Chinese, and the per-field test conditions — what was measured, at what voltage, under what load — are still in that language. Publishing them untranslated on an English dataset would undercut the care they document, so they wait for the translation pass rather than shipping half-readable. The machine-readable provenance they sit beside is complete today.