starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #2356] Add explicit support for custom fonts in PDF generation and sealing #661

New issue

Open

opened 2026-02-26 18:47:58 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 18:47:58 +03:00

Owner

Originally created by @dadastory on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/documenso/documenso/issues/2356

Describe the improvement you are suggesting in detail

Currently, when configuring fields (e.g. text fields, signature-related text, or dynamic content) in the document editor, the available options only allow adjusting position and font size. There is no way to configure font family or font style (such as selecting a specific font, or choosing bold/italic variants).

I suggest extending the field configuration options to include font-related settings, such as font family selection and basic font styles. This could be implemented as part of the field settings panel, similar to how size and positioning are currently handled.

Additional Information & Alternatives (optional)

In practical use, font style is an important part of document appearance and branding. The current limitation means that all fields are rendered using a default font, which may not match the original document’s typography or an organization’s brand guidelines.

This creates several pain points:

Users cannot visually align added fields with the surrounding document content.

Organizations with branding requirements cannot enforce consistent typography.

Documents may look unpolished or inconsistent even if layout and size are correct.

Adding support for font family and font style configuration would significantly improve the flexibility and professionalism of generated documents, while giving users finer control over how fields are rendered without changing their positioning logic.

Do you want to work on this improvement?

Please check the boxes that apply to this improvement suggestion.

I have searched the existing issues and improvement suggestions to avoid duplication.
I have provided a clear description of the improvement being suggested.
I have explained the rationale behind this improvement.
I have included any relevant technical details or design suggestions.
I understand that this is a suggestion and that there is no guarantee of implementation.

Originally created by @dadastory on GitHub (Jan 4, 2026). Original GitHub issue: https://github.com/documenso/documenso/issues/2356 ### Describe the improvement you are suggesting in detail Currently, when configuring fields (e.g. text fields, signature-related text, or dynamic content) in the document editor, the available options only allow adjusting position and font size. There is no way to configure font family or font style (such as selecting a specific font, or choosing bold/italic variants). I suggest extending the field configuration options to include font-related settings, such as font family selection and basic font styles. This could be implemented as part of the field settings panel, similar to how size and positioning are currently handled. ### Additional Information & Alternatives (optional) In practical use, font style is an important part of document appearance and branding. The current limitation means that all fields are rendered using a default font, which may not match the original document’s typography or an organization’s brand guidelines. This creates several pain points: Users cannot visually align added fields with the surrounding document content. Organizations with branding requirements cannot enforce consistent typography. Documents may look unpolished or inconsistent even if layout and size are correct. Adding support for font family and font style configuration would significantly improve the flexibility and professionalism of generated documents, while giving users finer control over how fields are rendered without changing their positioning logic. ### Do you want to work on this improvement? No ### Please check the boxes that apply to this improvement suggestion. - [x] I have searched the existing issues and improvement suggestions to avoid duplication. - [x] I have provided a clear description of the improvement being suggested. - [x] I have explained the rationale behind this improvement. - [x] I have included any relevant technical details or design suggestions. - [x] I understand that this is a suggestion and that there is no guarantee of implementation.

kerem added the

status: triage

label

2026-02-26 18:47:58 +03:00

kerem commented

2026-02-26 18:47:58 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 4, 2026):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jan 4, 2026): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#661

No description provided.

Rows
Columns