Pressure gradient converter
The freshwater benchmark of 0.433 psi per foot is 9794.7175457411 pascals per meter. Convert pressure gradients between oilfield and metric units for pore-pressure plots, fracture-gradient reports and hydrostatic design, always through pascals per meter. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 0.433
- From
- psi/ft
- To
- pa/m
- Result
- 9,794.7175457411 Pa/m
- Input
- 0.433
- Pa per m
- 9,794.7175457411
Need a reliable pressure gradient converter for oilfield pore-pressure work, hydrostatics, or geotechnical design? Enter a numeric gradient, choose the source unit and the target unit, and get an exact conversion among pascals per meter, pounds per square inch per foot, bar per meter, kilopascals per meter and related engineering units.
Which pressure-gradient units you can convert
This pressure gradient converter focuses on the units that appear most often in petroleum engineering, civil hydrostatics and process design. Pascals per meter (Pa/m) is the SI hub: one pascal of pressure change per meter of depth or length. Kilopascals per meter and megapascals per meter scale that hub for denser fluids and high-pressure wells.
Bar per meter and millibar per meter match European process and meteorology-style reporting. Atmospheres per meter appear in older textbooks. On the imperial side, pounds per square inch per foot (psi/ft) is the workhorse oilfield unit for pore pressure, fracture gradient and overburden gradient; freshwater is about zero point four three three psi per foot, and that figure is the benchmark many drillers memorize.
Psi per meter and psi per inch cover shorter-interval instrumentation. Bar per foot, kPa per foot, MPa per foot, Pa per foot and atm per foot complete the cross-system set so mixed metric-imperial reports can be normalized without hand math. Identical-unit requests simply echo the value after validation, which is useful when you only need a known unit check in a pipeline.
How conversion and exact factors work
Every conversion multiplies the input into pascals per meter, then divides by the target unit factor. That single-hub pattern avoids stacking rounding errors when you jump from psi per foot to bar per meter or from kPa per meter to psi per foot.
Factors are exact definitions, not fitted approximations: one foot is exactly zero point three zero four eight meters, one inch is exactly zero point zero two five four meters, one bar is exactly one hundred thousand pascals, and one standard atmosphere is exactly one hundred one thousand three hundred twenty-five pascals. One pound-force per square inch uses the international yard-and-pound definition of the pound-force and the inch, yielding six thousand eight hundred ninety-four point seven five seven two nine three one six eight three six one pascals.
Dividing that by zero point three zero four eight meters produces the exact psi-per-foot to Pa-per-meter factor used here.
What you can do with it
Oilfield pore-pressure and frac-gradient reports
Normalize mixed psi/ft and kPa/m gradients from offset wells into one unit before plotting or comparing to mud weight.
Pipeline and hydrostatic design checks
Convert bar/m or Pa/m design gradients to the unit your client’s specification or code checklist requires.
FAQ
What is a typical freshwater pressure gradient?
About 0.433 psi/ft, which converts to roughly 9.79 kPa/m or 9795 Pa/m with the exact factors used here. Always confirm the fluid density your design assumes.
How do I convert psi per foot to pascals per meter?
Multiply by 6894.757293168361 pascals per psi and divide by 0.3048 meters per foot. That is the factor applied here, so 0.433 psi per foot becomes 9794.7175457411 pascals per meter.
Which pressure gradient units can I convert?
Pascals, kilopascals, megapascals, bar, millibar and atmospheres per meter, psi per foot, per meter and per inch, plus bar, kPa, MPa, Pa and atmospheres per foot for mixed metric and imperial reports.
Why does every conversion pass through pascals per meter?
Using one hub avoids stacking rounding errors when you jump from psi per foot to bar per meter or the other way. Each factor is an exact definition, such as the foot of 0.3048 meters and the bar of 100000 pascals.
Where is psi per foot used?
It is the everyday oilfield unit for pore pressure, fracture gradient and overburden gradient. Converting offset-well data into one unit makes it easy to plot gradients side by side and compare them with mud weight.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/pressure-gradient \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":0.433,"from":"psi/ft","to":"pa/m"}'const res = await fetch("https://api.kit.forhosting.com/conv/pressure-gradient", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 0.433,
"from": "psi/ft",
"to": "pa/m"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/pressure-gradient",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 0.433,
"from": "psi/ft",
"to": "pa/m"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/pressure-gradient", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":0.433,"from":"psi/ft","to":"pa/m"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":0.433,"from":"psi/ft","to":"pa/m"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/pressure-gradient", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 0.433,
"from": "psi/ft",
"to": "pa/m"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.pressure_gradient",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Run it free in the browser or call the identical logic through the API at $0.002 per request with no subscription and no model inference.
Which pressure-gradient units you can convert
Short aliases and underscore forms such as psi_per_ft or pascals_per_meter are accepted and normalized to a canonical slash form in the response.
How conversion and exact factors work
There is no network call, no model inference and no clock dependency: the same input always produces the same JSON. Unknown units raise invalid_input naming the field and listing supported units, so bad client data is never charged as a successful conversion.
Using the API, pricing and delivery
Call the capability with three fields: value as a finite number, from as the source unit string, and to as the target unit string. Status is beta while the surface stabilizes, but the arithmetic itself follows fixed SI definitions and will not change under the same inputs. The response includes the numeric input, the canonical from and to unit keys, the converted result, a human-readable unit label such as psi/ft or Pa/m, and the intermediate pa_per_m value so auditors can recompute the step by hand or chain further conversions offline. Pricing for the hosted API is a flat $0.002 per successful request; failed validation such as a missing field or an unknown unit does not consume balance. For pipelines, submit each conversion as an independent task and collect results through your usual webhook or signed link flow. Keep source and destination units explicit in your integration rather than parsing free-text symbols: that contract keeps SDK types, OpenAPI schemas and form controls aligned, and it prevents silent misreads when a feed mixes metric and imperial labels.
Integration use cases
Engineering homework and unit tests
Assert exact conversions between imperial and SI pressure gradients in graded exercises and continuous-integration fixtures.
Technical questions
Which pressure gradient units are supported?
Pa/m, kPa/m, MPa/m, bar/m, mbar/m, atm/m, psi/m, psi/ft, psi/in, bar/ft, kPa/ft, MPa/ft, Pa/ft and atm/ft, plus common aliases. Unknown units return invalid_input.
How much does the pressure gradient converter API cost?
Each successful API call costs $0.002. The same converter runs free in your browser with no account required.
Is the conversion deterministic?
Yes. The math uses fixed SI factors through Pa/m and ten-decimal rounding, so the same input always yields the same JSON result.
What happens if I send an unknown unit?
The request fails with invalid_input explaining that the unit is unknown and listing supported values. Invalid client input is not charged.