--- title: "Add visible vs non-visible digital signature in Android | Nutrient" canonical_url: "https://www.nutrient.io/guides/android/signatures/digital-signatures/signature-lifecycle/signature-appearance/" md_url: "https://www.nutrient.io/guides/android/signatures/digital-signatures/signature-lifecycle/signature-appearance.md" last_updated: "2026-05-15T19:10:04.920Z" description: "Learn how to customize your digital signature appearance effectively. Enhance your documents with a professional touch and streamline your signature lifecycle." --- # Configure digital signature appearance in Android: Visible vs. non-visible signatures Nutrient offers comprehensive support for creating digital signatures, encompassing both visible and invisible signatures. The primary distinction between these two types lies in the customizable appearance aspect. Visible digital signatures, as the name suggests, are visually represented on a document, allowing users to easily identify and interact with them. Meanwhile, invisible digital signatures remain hidden within a document, leaving no visual trace. However, both types of signatures provide the same level of security and validity, ensuring the integrity of a digital document. ## Visible digital signatures To see how visible digital signatures function in practice, you can explore our demo. [Launch Demo](https://www.nutrient.io/demo/visible-digital-signatures) The structure of a signature field is organized in a particular format that provides essential information regarding the signature. It consists of three sections, as shown in the following diagram. 1. **Left side (signer’s name or signature graphic)** — This side displays the signer’s name or an illustration associated with the signer, like its handwritten signature. 2. **Right side (description)** — This side displays the signature description. The text included here can provide detailed information about the signature, such as the reason it was created or the date and time it was created. 3. **Center** — The central part of the signature field showcases a watermark. This watermark can be used for various purposes but is conventionally used to display a company logo. This gives the document an additional layer of branding. To configure the appearance of a signed document using the [`SigningManager.signDocument`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-signing-manager/sign-document.html) function, create a [`DigitalSignatureMetadata`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-digital-signature-metadata/index.html) object and customize the [`signatureAppearance`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-signature-appearance/index.html) field. With the `SignatureAppearance` object, you can customize various visual properties, outlined below. - Set the [`SignatureAppearanceMode`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-signature-appearance/-signature-appearance-mode/index.html). This can be one of: - `SIGNATURE_ONLY` — Only the signature is displayed. - `SIGNATURE_AND_DESCRIPTION` — Both the signature and a description are displayed. This is the default. - `DESCRIPTION_ONLY` — Only the description is displayed. - Set a [`SignatureGraphic`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-signature-graphic/index.html) — Optionally use a bitmap or PDF for the signature appearance. - Show/hide signer name. - Show/hide location. - Show/hide date. - Show/hide Nutrient watermark. The [`DigitalSignatureMetadata`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-digital-signature-metadata/index.html) object can be set on [`SignerOptions`](https://www.nutrient.io/api/android/nutrient/com.pspdfkit.signatures/-signer-options/index.html), which is then passed to `signDocument` for signing. For example: ```kotlin // Configure appearance. val appearance = SignatureAppearance( signatureAppearanceMode = SignatureAppearanceMode.SIGNATURE_ONLY ) // Configure the metadata. val metadata = DigitalSignatureMetadata( signatureAppearance = appearance //.. Add other metadata here, for example `TimestampData` ) // Create the options object. val signerOptions = SignerOptions.Builder(field, outputFile).setPrivateKey(key).setSignatureMetadata(metadata).build() // Sign the document. SigningManager.signDocument( context = context, signerOptions = signerOptions, type = digitalSignatureType, onFailure = {} ) { // On success. } ``` The table below shows an example of what each signature appearance mode looks like by default. | Signature Mode | Example | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `signatureOnly` | | | `descriptionOnly` | | | `signatureAndDescription` | | By default, the signature watermark is set to the Nutrient logo. If you want to remove the watermark, set `showWatermark` to `false`. If you want to use a different logo, customize the `watermarkImage` property. Supported file types for the logo are PDF, JPEG, and PNG. The other properties (`showSigner`, `showReason`, `showLocation`, and `showSignDate`) configure whether the signer’s name, reason, location, and sign date should be displayed, respectively. Here’s how to address common use cases with the signature appearance configuration: - **Creating a Custom Signature Design** — If you’d like to deliver your own signature design, configure the `signatureMode` as `signatureOnly`. Then, provide a PDF watermark, which fills the entire signature field with your unique design. - **Avoiding Image Overlap with Text** — If you want to ensure your text and images don’t overlap, configure `signatureMode` as `signatureAndDescription`. Then, use the `graphic` property to set the image. This configuration prevents overlap and ensures that each section of the signature retains its readability, helping to maintain a clear and organized display of information. ## Invisible digital signatures Invisible digital signatures don’t have any appearance. As described in the [add a signature field](https://www.nutrient.io/guides/android/signatures/digital-signatures/signature-lifecycle/add-a-signature-field.md) guide, you can create an invisible digital signature by setting its `boundingBox` property to have a `width` and `height` of zero. This ensures that the signature remains hidden from view but still retains its cryptographic properties and validity. To see how invisible digital signatures function in practice, you can explore our demo. [Try for Free](https://www.nutrient.io/try) [Launch Demo](https://www.nutrient.io/demo/invisible-digital-signatures) --- ## Related pages - [How to add signature fields to PDFs on Android](/guides/android/signatures/digital-signatures/signature-lifecycle/add-a-signature-field.md) - [External signing services on Android](/guides/android/signatures/digital-signatures/signature-lifecycle/external-signing-service.md) - [Biometric signatures on Android](/guides/android/signatures/digital-signatures/signature-lifecycle/biometric.md) - [Master digital signatures in Android efficiently](/guides/android/signatures/digital-signatures/signature-lifecycle/overview.md) - [Sign a PDF with a certificate on Android](/guides/android/features/digital-signatures.md) - [How to create and validate digital signatures on Android](/guides/android/signatures/digital-signatures/signature-lifecycle/prepare-the-certificates-for-signing.md) - [Securely validate digital signatures in Android apps](/guides/android/signatures/digital-signatures/signature-lifecycle/validation.md)