Picomolar to Nanomolar Converter
Common Conversions
| pM | nM |
|---|---|
| 1 | 0.001 |
| 5 | 0.005 |
| 10 | 0.01 |
| 50 | 0.05 |
| 100 | 0.1 |
| 250 | 0.25 |
| 500 | 0.5 |
| 1000 | 1 |
| 5000 | 5 |
| 10000 | 10 |
| 100000 | 100 |
| 1000000 | 1000 |
Why this conversion matters in chemistry
Picomolar values show up mostly in high-affinity biophysics — antibody Kd's in the low pM range, or cytokine levels at physiological concentrations. Nanomolar is one ladder rung up, where functional cellular assays tend to live. A purified-protein binding study might report a 50 pM Kd; a cell-based potency measurement on the same ligand typically lands two or three orders of magnitude higher because cells add avidity, membrane partitioning, and signal amplification. Converting 50 pM to 0.05 nM is the arithmetic; the useful mental model is that tight binding in a test tube rarely translates one-to-one to potency in a cell.
Formula
Where the factor comes from
Both symbols decorate mol/L, and mol/L is itself a chemist's convenience rather than a coherent SI unit — the coherent form would be mol/m³, with one mol/L equal to 1000 mol/m³. That choice has no bearing on the factor, because whichever volume unit sits beneath the mole appears identically on both sides and cancels. What survives is the prefix ratio and nothing else. Pico is 10⁻¹², nano is 10⁻⁹, and both were fixed by resolution of the General Conference on Weights and Measures in 1960, so 10⁻¹² ÷ 10⁻⁹ = 10⁻³ exactly. Divide a picomolar figure by 1000 and the same physical quantity is now written in nanomolar. No experiment will revise that number, and it propagates no uncertainty into anything downstream.
Precision and significant figures
Division by an exact 1000 moves the decimal three places and leaves the figure count untouched: 50 pM is 0.050 nM, two figures either way, and writing 0.05 nM quietly discards one. The harder question is what the picomolar number was worth to begin with. Surface plasmon and interferometry instruments report low-picomolar dissociation constants routinely, but a Kd well below the lowest analyte concentration actually titrated is inferred from a binding curve that sits near saturation across the whole titrated range, where almost no curvature is left to constrain it. Two significant figures is generous there. A stock concentration verified by absorbance against a molar extinction coefficient carries its own few-percent uncertainty on top of that.
Worked Examples
The clean anchor. 1000 pM in 1 nM is the equivalence worth keeping mental.
A single picomolar. Real concentrations this dilute usually show up in detection-limit contexts rather than deliberate dosing.
A sub-nanomolar Kd — the kind of affinity you'd see for a tuned-up antibody or a high-affinity receptor ligand.
A notably tight binder. At this affinity you're close to the limit of what a typical enzyme assay can resolve.
Common mistakes
The factor applied in the wrong direction
Going from picomolar to nanomolar makes the number smaller, and the reflex to multiply by 1000 rather than divide produces a millionfold discrepancy against the intended value. A plan calling for 250 pM that gets prepared at 250 nM looks entirely reasonable on paper. Sanity-check against the anchor — 1000 pM is 1 nM — before any dilution series is built from the figure.
Ligand depletion at picomolar loading
When the binding partner is present at a concentration comparable to the ligand, a substantial fraction of what you added ends up bound, and the free concentration is no longer the nominal one. The converted nanomolar figure describes what went into the tube, not what remained available. Binding curves that shift with receptor loading rather than staying fixed are usually reporting depletion.
Mixed units in one comparison table
Compiling potency data across papers produces columns where some entries arrived in pM and others in nM, and a sort or a plot treats the raw numbers as comparable. A 500 in one row and a 0.5 in another are the same concentration. Convert the whole column to a single unit before ranking anything, and label the header with that unit.