Is PressureTrend free to use?

Yes. The core tool is currently free for everyone.

Does PressureTrend upload my pressure data or test results?

Nothing is sent to any external server for analysis. All file parsing, calculations, chart rendering, and report generation runs entirely in your web browser. Beyond loading the page itself, only aggregated usage analytics are collected—no pressure data, test results, or file contents are ever transmitted. No data upload: Your pressure logs and results never leave your browser. Works well offline: While the page stays open, import, analysis, and PDF export continue without an internet connection. Session persistence: Your work is saved locally. You can refresh the page and continue where you left off. You control your exports: Only you decide when to generate a PDF report or save a project file.

Can I use PressureTrend offline?

While the page stays open, import, analysis, and PDF export continue without an internet connection.

Do I need to install any software?

No installation is required. PressureTrend runs directly in your web browser after you export CSV or Excel from your logger software.

Is my work saved if I refresh the page?

Your work is saved locally. You can refresh the page and continue where you left off.

Which file formats are supported?

Keller: LOGGER_5, LEO Record, and PressureSuite exports (CSV · Excel). Auto-detects native Keller layouts on CSV and Excel. Import setup picks channel and time source when several are present. Crystal nVision: Standard nVision CSV and Excel exports (CSV · Excel). Pressure time series with run metadata on CSV and Excel. Import setup confirms gauge serial and calibration when the file lists several. Wonderware: Trend / historian CSV exports (CSV). Trend exports with timestamp and tag columns. Pressure columns are discovered automatically; import setup confirms the right ones when several are present. Other tabular exports: Flexible column fallback (CSV · Excel). When the file is not a known native layout, detection tries flexible time and pressure columns so many logger exports still import without a dedicated parser.

My file is not recognised automatically. What should I do?

Confirm time calibration and test start before analysis. If your file contains multiple time sources, gauges, or pressure channels, pick the correct ones—standard Keller and nVision exports rarely need extra choices. If your logger export is not recognised well, email contact@pressuretrend.com with your device and export format—we improve parser support for CSV and Excel from real user files without accessing your data.

Can I import multiple files at the same time?

Yes. You can queue and work with up to 10 files per session.

Which Keller and Crystal devices are supported?

Keller: LOGGER_5, LEO Record, and PressureSuite. Pressure time series with run metadata on CSV and Excel. Import setup confirms gauge serial and calibration when the file lists several. When the file is not a known native layout, detection tries flexible time and pressure columns so many logger exports still import without a dedicated parser.

How does the pass/fail logic work?

Passed or Not passed combines pressure change against your criteria %, optional minimum test pressure, and delta trend (on falling holds and stable holds with a net loss). Falling hold: pass when drop ≤ criteria %. Rising hold: pass when rise ≤ criteria %. Stable hold: pass when |change| ≤ criteria %. If allow below test pressure is off, pressure anywhere in the window must stay at or above the nominal test pressure. That check is separate from drop % or rise %. Start-to-end change vs criteria %; minimum test pressure can fail independently. Direction ↓ / ↑ / — when |change| is below 0.05% of start pressure. Delta colours show flattening vs steepening; red deltas can fail ↓ holds and — holds with net loss.

Can I adjust the pass/fail criteria?

Set start and end of your hold test on the chart; set nominal test pressure, criteria %, and 2–8 delta checkpoints in the test controls beside it. Optional minimum floor pressure can fail the test independently.

How do I export my results?

Review pass/fail, start-to-end change, delta trends, and temperature insight in the workspace. Export a PDF via your browser print dialog or save a JSON project file to continue later.

What are the coloured deltas in the results?

Green: this step’s |Δ| is not steeper than the previous step (flattening or stable rate of change). Red: the interval change grew compared with the step before. On falling holds—and stable holds with a net pressure loss—a red delta can fail the test. On rising holds, red deltas are advisory only (Δ advisory).

How is drop % calculated on a hold test?

Passed or Not passed combines pressure change against your criteria %, optional minimum test pressure, and delta trend (on falling holds and stable holds with a net loss). Falling hold: pass when drop ≤ criteria %. Rising hold: pass when rise ≤ criteria %. Stable hold: pass when |change| ≤ criteria %. ↑ next to the result means net pressure rose during the window; ↓ means it fell; — means the change was very small. A rising hold is common when the system warms. The app shows rise %, not a misleading negative drop %. Check temperature and your band limits before signing off a warming hold.

Does API 16C allow 5% pressure variation during a hold?

API 16C hydrostatic hold acceptance commonly requires no visible external leakage and that pressure during the hold does not vary by more than 5% or 500 psi, whichever is less. Your job is governed by the approved procedure and the API edition cited on your test pack—verify exact wording there. In PressureTrend, set criteria % in the test controls (for example 5%) and evaluate drop or rise over your hold window; when the dual limit applies, also check the absolute 500 psi cap against start pressure before sign-off.

Is PressureTrend a replacement for CrystalControl or PressureSuite?

No. Those tools export the data from your logger. PressureTrend analyses the export, helps you read pass/fail, and builds a hold-test report.

Where is my data processed?

All file parsing, calculations, chart rendering, and report generation runs entirely in your web browser. Beyond loading the page itself, only aggregated usage analytics are collected—no pressure data, test results, or file contents are ever transmitted.

Who can see my pressure test data?

Nothing is sent to any external server for analysis. Your pressure logs and results never leave your browser.

Is PressureTrend suitable for offshore use?

While the page stays open, import, analysis, and PDF export continue without an internet connection. Local browser processing suits restricted connectivity and sensitive environments.

My logger export doesn't work well. Can you help?

We actively improve support for different logger formats. Reach out with your device and export format—we improve parsers from real user files without accessing your data.

Where can I find more help?

Start-to-end change vs criteria %; minimum test pressure can fail independently. Pass/fail, hold direction (↑ ↓ —), delta colours, temperature, and test-pressure checks—the same rules as the result card. See the full guide for hold direction, delta colours, temperature, and test-pressure checks. Logger workflow guides live on the Guides page and in Resources below.

Open-source licenses

PressureTrend is built with open-source libraries. The table below lists production dependencies and their SPDX or license identifiers as reported by each package.

Last updated: 10 June 2026

Notice

This list is generated automatically from installed npm packages at build time. License strings come from each package’s metadata and may not constitute the full license text.

For the complete license terms of a package, refer to the package source or the repository link when available.

88 production packages · generated 10 June 2026

Package	Version	License	Source
@date-fns/tz	1.5.0	MIT	Repository
@img/colour	1.1.0	MIT	Repository
@img/sharp-libvips-linux-x64	1.2.4	LGPL-3.0-or-later	Repository
@img/sharp-linux-x64	0.34.5	Apache-2.0	Repository
@napi-rs/canvas	0.1.100	MIT	Repository
@napi-rs/canvas-linux-x64-gnu	0.1.100	MIT	Repository
@next/env	15.5.18	MIT	Repository
@next/swc-linux-x64-gnu	15.5.18	MIT	Repository
@opentelemetry/api	1.9.1	Apache-2.0	Repository
@opentelemetry/api-logs	0.208.0	Apache-2.0	Repository
@opentelemetry/core	2.2.0	Apache-2.0	Repository
@opentelemetry/core	2.7.1	Apache-2.0	Repository
@opentelemetry/exporter-logs-otlp-http	0.208.0	Apache-2.0	Repository
@opentelemetry/otlp-exporter-base	0.208.0	Apache-2.0	Repository
@opentelemetry/otlp-transformer	0.208.0	Apache-2.0	Repository
@opentelemetry/resources	2.2.0	Apache-2.0	Repository
@opentelemetry/resources	2.7.1	Apache-2.0	Repository
@opentelemetry/sdk-logs	0.208.0	Apache-2.0	Repository
@opentelemetry/sdk-metrics	2.2.0	Apache-2.0	Repository
@opentelemetry/sdk-trace-base	2.2.0	Apache-2.0	Repository
@opentelemetry/semantic-conventions	1.41.1	Apache-2.0	Repository
@posthog/core	1.29.9	MIT	Repository
@posthog/react	1.9.1	MIT	Repository
@posthog/types	1.376.0	MIT	Repository
@protobufjs/aspromise	1.1.2	BSD-3-Clause	Repository
@protobufjs/base64	1.1.2	BSD-3-Clause	Repository
@protobufjs/codegen	2.0.5	BSD-3-Clause	Repository
@protobufjs/eventemitter	1.1.1	BSD-3-Clause	Repository
@protobufjs/fetch	1.1.1	BSD-3-Clause	Repository
@protobufjs/float	1.0.2	BSD-3-Clause	Repository
@protobufjs/inquire	1.1.2	BSD-3-Clause	Repository
@protobufjs/path	1.1.2	BSD-3-Clause	Repository
@protobufjs/pool	1.1.0	BSD-3-Clause	Repository
@protobufjs/utf8	1.1.1	BSD-3-Clause	Repository
@swc/helpers	0.5.15	Apache-2.0	Repository
@types/node	22.19.19	MIT	Repository
@types/react	19.2.15	MIT	Repository
@types/trusted-types	2.0.7	MIT	Repository
@vercel/analytics	2.0.1	MIT	Repository
adler-32	1.3.1	Apache-2.0	Repository
caniuse-lite	1.0.30001793	CC-BY-4.0	Repository
cfb	1.2.2	Apache-2.0	Repository
client-only	0.0.1	MIT	—
clsx	2.1.1	MIT	Repository
codepage	1.15.0	Apache-2.0	Repository
core-js	3.49.0	MIT	Repository
crc-32	1.2.2	Apache-2.0	Repository
csstype	3.2.3	MIT	Repository
date-fns	4.2.1	MIT	Repository
detect-libc	2.1.2	Apache-2.0	Repository
dompurify	3.4.5	(MPL-2.0 OR Apache-2.0)	Repository
echarts	5.6.0	Apache-2.0	Repository
echarts-for-react	3.0.6	MIT	Repository
fast-deep-equal	3.1.3	MIT	Repository
fflate	0.4.8	MIT	Repository
frac	1.1.2	Apache-2.0	Repository
long	5.3.2	Apache-2.0	Repository
nanoid	3.3.12	MIT	Repository
next	15.5.18	MIT	Repository
papaparse	5.5.3	MIT	Repository
pdfjs-dist	5.7.284	Apache-2.0	Repository
picocolors	1.1.1	ISC	Repository
postcss	8.4.31	MIT	Repository
posthog-js	1.376.0	MIT*	Repository
preact	10.29.2	MIT	Repository
pressuretrend	0.1.0	UNLICENSED	—
protobufjs	7.6.1	BSD-3-Clause	Repository
query-selector-shadow-dom	1.0.1	MIT	Repository
react	19.2.6	MIT	Repository
react-dom	19.2.6	MIT	Repository
scheduler	0.27.0	MIT	Repository
semver	7.8.0	ISC	Repository
sharp	0.34.5	Apache-2.0	Repository
size-sensor	1.0.3	ISC	Repository
source-map-js	1.2.1	BSD-3-Clause	Repository
ssf	0.11.2	Apache-2.0	Repository
styled-jsx	5.1.6	MIT	Repository
tailwind-merge	3.6.0	MIT	Repository
tslib	2.3.0	0BSD	Repository
tslib	2.8.1	0BSD	Repository
undici-types	6.21.0	MIT	Repository
web-vitals	5.2.0	Apache-2.0	Repository
wmf	1.0.2	Apache-2.0	Repository
word	0.3.0	Apache-2.0	Repository
xlsx	0.18.5	Apache-2.0	Repository
zod	3.25.76	MIT	Repository
zrender	5.6.1	BSD-3-Clause	Repository
zustand	5.0.13	MIT	Repository