# Store CUE data in metadata
**URL:** https://community.mp3tag.de/t/store-cue-data-in-metadata/70090
**Category:** Support
**Created:** [November 6, 2025, 7:29am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090 "2025-11-06T07:29:08Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@user648645](https://community.mp3tag.de/u/user648645)
#### Post date: [November 6, 2025, 7:29am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/1 "2025-11-06T07:29:08Z")
Hi everyone,
I have several compilation CDs ripped as a single FLAC or MP3 file. They include a separate CUE file. I hardly ever use the CUE file. I play the audio files directly in an audio player. The CUE files are of course always visible in Windows explorer (they are in the same directory as the audio file), and I find them unnecessary. I only want to see the audio files. However, I don't want to delete the CUE files because I might want to use them in the future.
In order to keep the CUE files but hide them in Windows Explorer, I want to store the cue file data in the audio file's metadata. Is this a good idea?? Sometimes they are large text files, and I don't know if this is supported. I'm thinking of putting the CUE information in the comments field.
Is this okay to do?
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 6, 2025, 7:31am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/2 "2025-11-06T07:31:42Z")
You can also store the whole data in a user-defined field like e.g. CUE\_SHEET.
As there is no standard field for your purpose, you can do whatever you want.
Yet, using a standard field my lead to problems with other applications.
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 6, 2025, 7:36am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/3 "2025-11-06T07:36:50Z")
> [@user648645](#):
>
> Is this okay to do?
Technically speaking: Yes, you can do that.
However, I would not recommend that. You still need the same amount of storage space.
If you just want to hide these files, set the "hidden" attribute on your CUE files.
In your case it would be something like
`attrib +h *.cue`
> **[attrib](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/attrib)**
>
> Reference article for the attrib command that displays, sets, or removes attributes assigned to files or directories.
This means that you will no longer see your CUE files in Windows File Explorer.
You can remove the hidden attribute with
`attrib -h *.cue`
Alternatively, you can configure your Windows File Explorer to display hidden files too.
---
### Author:  [@user648645](https://community.mp3tag.de/u/user648645)
#### Post date: [November 6, 2025, 8:16am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/4 "2025-11-06T08:16:02Z")
@LyricsLover What is the reason you don't recommend this? Is a user defined field an idea like ohrenkino says?
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 6, 2025, 8:23am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/5 "2025-11-06T08:23:23Z")
IMHO, you won't gain anything (beside "I don't see the CUE files anymore in Windows File Explorer").
If you
> [@user648645](#):
>
> find them unnecessary
then delete them.
If you
> [@user648645](#):
>
> want to use them in the future
then leave them as they are.
I can't see any advantage in hiding the CUE files by moving them inside the music files.
The aforementioned user-defined field is, of course, a valid idea.
Personally, I would just not use it. 😉
---
### Author:  [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [November 6, 2025, 8:39am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/6 "2025-11-06T08:39:49Z")
**Small addition:**
If you use FLAC files, you could use
`metaflac.exe --import-cuesheet-from=album.cue album.flac`
this would embed your information as a special `CUESHEET` block.
Source: [Documentation](https://xiph.org/flac/documentation_tools_metaflac.html).
Compatibility with players may vary.
See also here:
> [@Working with CUESHEET blocks in FLAC files - detect and remove](https://community.mp3tag.de/t/working-with-cuesheet-blocks-in-flac-files-detect-and-remove/64368/2):
>
> Yes — metaflac or foobar2000 is the way to go here. The cuesheet is not part of the actual FLAC tag (which is Vorbis Comments or METADATA\_BLOCK\_VORBIS\_COMMENT), but resides in a different block type called [METADATA\_BLOCK\_CUESHEET](https://xiph.org/flac/format.html#metadata_block_cuesheet). That's also the reason why it's not visible in extended tags. I've added it to my list of future ideas for improvement.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [December 6, 2025, 8:40am UTC](https://community.mp3tag.de/t/store-cue-data-in-metadata/70090/7 "2025-12-06T08:40:43Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.