How to save and store electronic signatures in Flutter

Managing electronic signatures effectively is crucial for many document workflows. Nutrient Flutter SDK provides a comprehensive solution for signature storage, allowing users to save signatures for reuse across multiple documents. This guide will walk you through the available options for configuring signature storage in your Flutter application.

Signature saving strategy

Nutrient Flutter SDK offers flexible options for managing signature storage through the SignatureSavingStrategy enum. When configuring your PDF viewer, you can specify how you want signatures to be handled after creation:

PspdfkitWidget(
  documentPath: 'path/to/document.pdf',
  configuration: PdfConfiguration(
    signatureSavingStrategy: SignatureSavingStrategy.saveIfSelected,
    // Other configuration options...
  ),
)

Available strategies

Nutrient supports three signature saving strategies:

• SignatureSavingStrategy.neverSave — Signatures are never saved for reuse. This is suitable for one-time signature scenarios or when privacy is a priority, ensuring no signature data persists between sessions.

• SignatureSavingStrategy.alwaysSave — Signatures are always automatically saved for future use. This offers the most convenience for users who frequently sign documents, as their signatures will be available for reuse immediately.

• SignatureSavingStrategy.saveIfSelected — Signatures are only saved if the user explicitly opts to save them. This provides a balance between convenience and user control, allowing users to decide which signatures they want to keep.

Web limitations

While Nutrient Flutter SDK provides robust signature capabilities on web, the automatic signature saving and storage functionality isn’t yet bridged on the web platform. For web-specific signature implementation details, refer to:

• Nutrient Web SDK signatures guide

• Customizing Nutrient Flutter SDK