Sound Annotation Icon in Foxit/Chrome

Posted by: jsacks on 16 August 2021, 5:23 am EST

    • Post Options:
    • Link

    Posted 16 August 2021, 5:23 am EST

    I’m having an issue where I’m creating a sound annotation but the speaker icon is not visible in Foxit PhantomPDF and Chrome. It is visible in Acrobat and the GcPDF web viewer.

    In Foxit, I am able to hover over where it should be and the hand turns to a pointer, which I can then double click and it plays.

    From this, I am assuming that the Speaker icon is not actually embedded in the PDF, but rather is viewer-dependent (i.e. the viewer application must have a “Speaker” icon in its library.) This is supported by the speaker icon looking different on Acrobat and the GcPDF web viewer.

    So…I am wondering, is there a way I can embed a speaker image behind the sound annotation so that users with PDF viewers capable of playing sounds but not of displaying the Speaker icon can nevertheless still know that there’s a sound annotation there?

    I’m thinking I’d use the Speaker icon from the GcPDF web viewer, which would simply be covered up by the annotation icon if the PDF is opened in the web viewer. If opened in Foxit, the clickable sound annotation would be transparent on top of this image.

    What are your thoughts on this approach? If you think wise, is there an easy way to get the Speaker icon the web player uses besides hunting through the resources Chrome pulls down?

  • Posted 16 August 2021, 4:41 pm EST


    We are sorry for the inconvenience, we are able to replicate the issue and we have forwarded this to the concerned team for further investigation with the internal tracking id DOC-3569.

    We will let you know as we get an update on this.


    Manish Gupta

  • Posted 25 September 2021, 4:00 pm EST


    The issue related to showing the sound and file attachment annotation, is not supported by Chrome and the FoxIt Editor.

    Regarding If Printable is set to true, the sound attached to the sound annotation cannot be played,

    This issue has been fixed in the latest build 2.2.15. Please update it from the Npm packages,


    Manish Gupta

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels