Why do I see watermark when I enter a valid license key?

There are several possible reasons WebViewer may still display a watermark even when using a valid license. As a first step, we recommend opening the developer console and checking for any warnings or error messages as it will give you information about the license.

• Incorrect platform license
  Apryse licenses on a per-application, per-platform basis, where platform could be Android, Web, Windows, etc. Please double check that you are using a Web SDK license for the Web platform. Please see this forum post for more details:
  https://community.apryse.com/t/license-key-exception/3376

• Connection to the licensing server
  License keys that contain the letters PWS requires a connection to the licensing server. Please see this forum post for more details:
  https://community.apryse.com/t/pdftron-web-services-pws-timeout-error/5124

• License expiration
  Verify that the license key is not expired. The date is on the key in the format YYYYMMDD
  
  For PWS keys - If the PWS key is expired, you will see a watermark and a console error message after the expiry date.
  For OEM keys - If the OEM key is expired, you will not see a watermark, but you will no longer receive updates released after the expiration date.

• Incorrect key being passed
  Confirm that the license key is entered exactly into the WebViewer constructor.
  If you are using environment variables, verify by using a console log or set a breakpoint immediately before the WebViewer constructor to check that the key matches your intended license key.

• The document itself is watermarked
  If the PDF already contains watermark annotations or flattened text, the SDK will display them.

• Watermark applied programmatically
  Double check that you are not applying the watermark with the Web SDK via setWatermark API.

• Using WebViewer Server without a Server license
  If your deployment uses WebViewer Server and only your client-side (Web SDK) key is valid, you may still see watermarks on rasterized pages.
  See our guide for more information: https://docs.apryse.com/web/guides/wv-server-config#add-your-pdfnet-key

• Cached Builds
  Browser configurations can serve older versions of WebViewer builds which may not work nicely with updated licenses. Recommended to clear older cached builds.
  See the FAQ for more information: https://docs.apryse.com/web/faq/load-webviewer-files-no-cache