Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
tonimanetes opened this issue May 25, 2025 · 0 comments
Open
2 tasks done

Comments

@tonimanetes
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant