• You're one step from joining Bioinformatics Forums – Research, Tools, Code & Collaboration.
    Create a free account to post, follow threads, and never miss an update.  Sign up free →

merging paired-end FASTQ files

Hyperhyped

New member
Joined
Jun 14, 2025
Messages
3
City & State/Province
Massachusetts
I'm a beginner in bioinformatics, so I need some help. I'm working with pair-end FASTQ files which I trimmed. I tried to merge the paired reads, but the problem is that in some cases the overlap isn't complete? I either get overhangs or parts that don't have matching endings. Hope I explained this properly and I hope someone can help explain what to do?
 
I'm a beginner in bioinformatics, so I need some help. I'm working with pair-end FASTQ files which I trimmed. I tried to merge the paired reads, but the problem is that in some cases the overlap isn't complete? I either get overhangs or parts that don't have matching endings. Hope I explained this properly and I hope someone can help explain what to do?
There are some reads that just won't merge, especially if your fragments are longer than the combined read lengths. Try a tool like PEAR or BBMerge with relaxed settings, or skip merging and align as paired reads instead.
 
Yeah, that happens a lot with paired end reads after trimming, happens when the overlap isn't complete, some tools will struggle to merge it properly, leaving overhangs or unmatched tails. you should use a merge tool that can handle partial overlaps and allows some mismatch tolerance. like PEAR or BBMerge are pretty good at this
 
I'm a beginner in bioinformatics, so I need some help. I'm working with pair-end FASTQ files which I trimmed. I tried to merge the paired reads, but the problem is that in some cases the overlap isn't complete? I either get overhangs or parts that don't have matching endings. Hope I explained this properly and I hope someone can help explain what to do?
Yeah, like what the others said, it's common especially with varying read lengths or when the insert size distribution leads to situations where the reads don't fully overlap or have perfect complementarity in the overlap region. Tools like PEAR or FLASH should be able to handle this, and they often allow for some mismatches or an incomplete overlap when merging, while still trying to produce the longest possible contig. If you're getting overhangs or non-matching endings, it might indicate that your trimming was a bit aggressive, or that your merging parameters are too strict. You could try adjusting the minimum overlap required or allowing for a certain percentage of mismatches in the overlap region within your merging tool. Sometimes, you just can't perfectly merge everything, and it's okay to have some reads remain unmerged if they genuinely don't have sufficient overlap. I strongly recommend to focus on optimizing for the best possible outcome for the majority of your reads.
 
Back
Top