# Pen pressure curves

{% hint style="info" %}
Before you read this document, read: [Pen pressure response](/drawtab/core/pressure/pen-pressure-response.md)
{% endhint %}

## Overview

Your pen senses pressure and encodes it as a number. You can think of the number as ranging from 0 to the maximum number of pressure levels of your pen. In many cases its easier to "normalize" this number so that it ranges from 0.0 to 1.0. This makes discussing the pressure easier to understand in many cases.

This number flows through a "Pipeline" of components: tablet firmware -> tablet driver -> OS pen subsystem-> pen-aware application -> brush engine

Some of these components can process the the pressure - that means they can alter the number - before it is sent to the next component.

The processing of the pressure number alters how the pen will feel to draw with.

There are different ways in which components can process the pressure number. These include:

* Pressure processing curves (also called just "pressure curves")
* Pressure smoothing

This document deals with pressure processing curves.

## Response curve vs processing curve

Thinking of it as numbers:

* The pressure response curve is how the pen hardware handles pressure. It maps physical pressure into a pressure number.
* The processing curve is a mathematical operation that takes a pressure number and can change it into a different number.

Thinking of it as a behavior ("how the pen feels")

* The pressure response curve is the "native" behavior of how the pen feels to draw with.
* The pressure processing curve is a way of modifying that behavior.

## What a pressure processing curve looks like

For example in the Wacom Tablet Properties app it looks like this:

![](/files/xCA4X6opFcwpOAWiDU5X)

* The X axis labelled as "Pen pressure" is the logical input pressure
* The Y axis labelled as "Output" is the output logical pressure
* This particular curve bends down a little. But many other shapes are possible. Each shape has their uses.

## Popular coverage of pressure curves is misleading

You might encounter YouTube videos where people describe the pressure curve as the pressure behavior of the pen. This is completely inaccurate. The pressure curve describes how the pressure behavior (the pressure response) is being modified. You cannot look at a pressure curve and understand the pressure behavior of your pen. The only way for you to understand the pressure behavior of pen is to physically measure it with the scale and start mapping physical pressure values to logical pressure values.

## Pressure curve shapes

There are a variety of pressure curve shapes - each of which can solve some problem or achieve some visual effect.

<figure><img src="/files/4XwtcJx15cdSn6hzTwzb" alt=""><figcaption></figcaption></figure>

To see which drivers and apps support which shapes see this: [App pressure curves](/drawtab/core/pressure/pen-pressure-curves/pressure-curve-in-app.md)

## Things you can do with pressure curves

* [Null pressure curve](/drawtab/core/pressure/pen-pressure-curves/pressure-curve-null.md) - a curve that "does nothing"
* [Constraining pressure curve output](/drawtab/core/pressure/pen-pressure-curves/pressure-curve-constrain-output.md)
* [Constraining pressure curve input](/drawtab/core/pressure/pen-pressure-curves/pressure-curve-constrain-input.md)
* [Decreasing IAF](/drawtab/guides/customizing/lowering-iaf.md)
* [Increasing IAF](/drawtab/guides/customizing/increasing-iaf.md)
* [Lowering maximum physical pressure](/drawtab/guides/customizing/lowering-max-physical-pressure.md)

## Driver UX for pressure curves

See [Driver pressure curves](/drawtab/core/pressure/pen-pressure-curves/pressure-curves-in-drivers.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sevenpens.com/drawtab/core/pressure/pen-pressure-curves.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.