Log4Shell is a vulnerability found in the Log4j data logging package for the Java platform. MEGA is not developed using Java and does not use Log4j (or any other data logging software). The Log4Shell vulnerability is NOT known to affect MEGA. More information regarding the Log4Shell vulnerability can be found at apache.org/Log4j and wikipedia/Log4Shell.
Starting in macOS version 10.15 (Catalina), Apple has dropped support for 32-bit applications. For macOS 10.15 and all versions moving forward, MEGAX 10.1.4 and later must be used. However, earlier versions of MEGA can be ran on macOS 10.15 and later by using a Windows version of MEGA with virtualization software such as VMWareFusion.
For the following versions of macOS it is recommended to use MEGAX 10.0.0 or later:
MEGAX has not been tested on the following versions of macOS. Although MEGA7 has been tested on these versions, support is no longer provided for MEGA7:
If there is not a version of MEGA listed here that is compatible with your macOS system, any of the Windows versions of MEGA can be ran on macOS by using virtualization software such as VMWareFusion.
Starting in version 10.1.4, MEGAX has been updated to meet the more stringent requirements for running 3rd party applications that were introduced in macOS 10.15 (Catalina). You should download and install MEGAX 10.1.4 or later.
For basic instructions on using MEGA-CC, see the MEGA-CC-Quick-Start-Tutorial
No. MEGA is provided free of charge for all research and educational purposes. However, it is not permissible to redistribute MEGA in any form to other users. We require that all users download their own copy of MEGA from our website directly. MEGA is protected by all applicable copyright laws.
Because MEGA includes many statistical methods for the study of molecular evolution in an interactive framework, it is instructive for classroom teaching. If you are interested in using MEGA in the classroom/lab, there are no restrictions. Your students may download a copy from the website www.megasoftware.net or you may install copies on multiple computers in a common computing area. However, if you want to use MEGA in any other form, please contact the authors by e-mail ( firstname.lastname@example.org ).
If you are using MEGA in classroom teaching, please send us the following information by e-mail for our records ( email@example.com ).
To perform a silent install of MEGA on MS Windows computers, call the installer executable with the /SILENT and /VERYSILENT switches. For example:
MEGA*_setup.exe /SILENT /VERYSILENT
Then MEGA will be installed using the default options. The install will also probably need to be run with admin privileges so that the User Account prompt is not shown.
To perform a silent install of MEGA X on Linux systems, refer to the documentation for the package management software that you are using (probably either dpkg or rpm).
Yes, MEGA is provided free of charge for commercial institutions as well. However, it is not permissible to redistribute MEGA in any form to other users. We require that all users download their own copy of MEGA from our website directly. MEGA is protected by all applicable copyright laws.
Citation for MEGA X:
MEGA X: Molecular Evolutionary Genetics Analysis across computing platforms.
Kumar S, Stecher G, Li M, Knyaz C, and Tamura K (2018)
Molecular Biology and Evolution 35: 1547-1549.
- Download PDF
If using MEGA X on macOS, please cite this paper as well:
Molecular Evolutionary Genetics Analysis (MEGA) for macOS.
Stecher G, Tamura K, and Kumar S (2020)
Molecular Biology and Evolution (accepted).
- Download PDF
Citation for MEGA 7:
MEGA7: Molecular Evolutionary Genetics Analysis Version 7.0 for bigger datasets.
Kumar S, Stecher G, and Tamura K (2016)
Molecular Biology and Evolution 33(7):1870-1874.
- Download PDF
Citation for MEGA 6:
MEGA6: Molecular Evolutionary Genetics Analysis Version 6.0.
Tamura K, Stecher G, Peterson D, Filipski A, and Kumar S (2013)
Molecular Biology and Evolution 30: 2725-2729.
- Download PDF
Citation for MEGA 5:
MEGA5: Molecular Evolutionary Genetics Analysis using Maximum Likelihood, Evolutionary Distance, and Maximum Parsimony Methods.
Tamura K, Peterson D, Peterson N, Stecher G, Nei M, and Kumar S (2011)
Molecular Biology and Evolution 28: 2731-2739.
- Download PDF
Citation for MEGA-CC:
MEGA-CC: Computing Core of Molecular Evolutionary Genetics Analysis Program for Automated and Iterative Data Analysis.
Kumar S, Stecher G, Peterson D, and Tamura K (2012)
- Download PDF
Citation for MEGA 4:
MEGA4: Molecular Evolutionary Genetics Analysis (MEGA) software version 4.0.
Tamura K, Dudley J, Nei M & Kumar S (2007)
Molecular Biology and Evolution 24: 1596-1599.
- Download PDF
The authors of MEGA appreciate all forms of user suggestions and feedback. In order to properly address each suggestion, we encourage the use of the Suggestion Box form found in the Support/Feedback section of the MEGA website.
Please report the bug to the MEGA development team immediately using the Bug Report submission form on the MEGA website. User-submitted bug reports are invaluable to the MEGA development team. Due to limited resources, you may not receive a reply to your bug report immediately, but we can assure you that each bug report will be addressed and responded to as soon as possible by a member of the MEGA development team.
X11 is a program that comes with MacOS X and is essential for displaying the Wine and Wineskin versions of MEGA (MEGA7 and earlier) on the Mac. If you close X11 MEGA will close as well.
Yes, starting in version 4, we have built support for a multi-user environment, which will allow each user of the same computer to keep his/her customized settings, including file locations, window sizes, choice of genetic code table, and previously-used analysis options. This feature will facilitate educational and laboratory usage where a single computer is often shared by multiple users.
Simply right-click on the file with the FAS extension to navigate to the properties item. You can then select the program that you wish to associate with that extension.
You must identify which taxa have no common sites with others, and then remove them in order to continue your computing. Please follow this procedure to check the number of common sites between taxa:
The number in the matrix indicates the number of common sites between sequences that are available for analysis. When this number is zero, there are no common sites. To get around this problem, you may want to eliminate some sequences. In addition, the use of the "Pairwise-Deletion" option for handling alignment gaps and missing data may also be employed.
MEGA can only be used over the network if the directory where MEGA EXE is stored is available for reading (not writing). The user does not need writing privileges on the network. If your bug report indicates that you have an unreliable network connection, then it will be impossible to use MEGA reliably.
MEGA also writes temporary files in the User's Home Directory. This local directory will often be housed on the local computer (in which MEGA EXE is running), and it will always be available. A completely network-based use of MEGA (including User's Home Directory) will cause problems due the non-reliability of network connections (and thus temporary and setup files).
Go to your MEGA appdata directory eg. %appdata%/MEGAX_XXXXXXX\, then /Private/Ini/ and edit the ignore_updates.ini file. Change the 0 to a 1 .
If you are running the MEGA exe from a remote computer this should work too.
Many programs which write out their own files don't stick to the official file format format. This means MEGA has to be able to handle lots of slightly different implementations of the same file format.
We try our best to be able to convert all file formats but including formats which don't exactly match their format.
Check the file you want to convert, and make sure there are NO spaces in the taxa/sequence names as this often can cause issues.
MEGA does not compute or provide branch lengths for consensus tree, as they generally contain multi-furcations due to the partition frequency cut-offs. Estimates of branch lengths in these cases are not correct, as the collapsed partitions have non-zero lengths in reality but they are not statistically resolved (i.e., lack of significance by bootstrap method) so they are drawn accordingly on the screen.
Only the branching pattern from the bootstrap tree should be viewed as is, and the branch lengths should be what you see in the "Original Tree" tab.