musescore / musescore/MuseScore

Include score metadata (title, composer, copyright) as PDF metadata on export

Open
#28,144 10 comments 5 reactions 1 assignee View on GitHub

@YueZheng-Sea-angle is already working on this.

Since Sep 24, 2025.

community needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea
Feature Request

When exporting a score to PDF, MuseScore should embed the score's metadata (such as Title, Composer/Author, Copyright, etc.) into the PDF file's metadata fields.

This would make the PDF easier to catalog, search, and manage in document libraries or archives, and is consistent with how many publishing tools behave.

Benefits
  • Improves discoverability when opening the PDF in a viewer or organizing files.
  • Makes it easier to identify the author and source of the file without opening it.
  • Brings MuseScore closer to professional publishing standards.
Suggested behavior

Use the following mappings, for example:

  • PDF "Title" → MuseScore "Work Title"
  • PDF "Author" → MuseScore "Composer" (or combined composer/lyricist)
  • PDF "Subject" → MuseScore "Subtitle" (if present)
  • PDF "Copyright" → MuseScore "Copyright"
Additional info

Many PDF viewers (Adobe Reader, macOS Preview, etc.) display this metadata. Currently, MuseScore PDFs have blank or generic metadata.

Problem to be solved

When I export a score to PDF, the resulting file does not contain any useful metadata such as the title, composer, or copyright. This means that when I view the PDF in a reader or file browser, I can't easily identify or search for the score by its actual content.

This lack of metadata makes it harder to organize files, especially when managing a large collection of scores. It also reduces the usefulness of the exported PDF when shared with others or archived.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.