Title: Backup Changes Default Encoding
Last modified: August 18, 2016

---

# Backup Changes Default Encoding

 *  [paperlion](https://wordpress.org/support/users/paperlion/)
 * (@paperlion)
 * [21 years, 1 month ago](https://wordpress.org/support/topic/backup-changes-default-encoding/)
 * Noticed this when opening a 1-Click Backup (htm) file in a text editor. Note 
   the encoding reference, and that WordPress is set to UTF-8 (Unicode) by default
   and in this installation the backup was created from as well. Blogs in straight
   english and the like probably won’t notice anything, but many foreign characters
   and symbols are encoded differently in different character sets:
 * `<META http-equiv=Content-Type content="text/html; <strong>charset=iso-8859-1
   </strong>">`
 * Does anyone know if there a way to insure against re-encoding on backups as it
   seems is ordinarily done, as indicated here?
 * Footnote: Do phpmyadmin, mySQL, 1-click restore, or WP itself fool around with
   encoding in any way on a restore also?

The topic ‘Backup Changes Default Encoding’ is closed to new replies.

 * 0 replies
 * 1 participant
 * Last reply from: [paperlion](https://wordpress.org/support/users/paperlion/)
 * Last activity: [21 years, 1 month ago](https://wordpress.org/support/topic/backup-changes-default-encoding/)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics