# Please try again with a to compatible zip file

**URL:** <https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555>\
**Category:** Support\
**Tags:** windows-10\
**Created:** [August 12, 2023, 4:23pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555 "2023-08-12T16:23:41Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 4:23pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/1 "2023-08-12T16:23:41Z")

</div>

Hello,  
I am trying to import a website to Local but it is just unsuccessfull. I’ve got a message saying “please try again with a compatible zip file”.  
Please could you check and tell me if something is missing in the screenshot attached?  
Thanks

 ![Capture d’écran (5)](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/2/e/2e9f2199a8c9f36d2e6f1e8bcc8cd57d0d2e2ead.png)

* * *

### System Details

- **Local Version:**

- **Operating System (OS) and OS version:**

* * *

### Local Logs

Attach your Local Logs here ([Help Doc - Retrieving Local’s Log](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/))

* * *

_ **Security Reminder** _  
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 4:39pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/2 "2023-08-12T16:39:56Z")

</div>

Hi @Mike4!

Where is the site coming from originally?

Can you try just pulling out the `wp-content` and `SQL` directories and zipping those up together to import?

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 4:48pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/3 "2023-08-12T16:48:17Z")

</div>

The site comes from my live hosting. I wanted to work on it locally instead of putting it in maintenance mode  
The sql is not already in the wp-content then?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 4:52pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/4 "2023-08-12T16:52:09Z")

</div>

Sometimes there can be extra files in a site export that can confuse Local during the import process. As a baseline what it needs to get a site going are the WP-Content and SQL directories so sometimes reducing your import file down to just those two items can help it to go through. Another thing you could do is use the free plugin WP Migrate Lite to create a new export of your hosted site that only includes these files.

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 5:03pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/5 "2023-08-12T17:03:46Z")

</div>

Is there a limit in MB to use this plugin?

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 5:22pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/6 "2023-08-12T17:22:26Z")

</div>

Is that just a copy that I am going to export or its going to really remove the site from where it is and export it?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 5:26pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/7 "2023-08-12T17:26:31Z")

</div>

```auto
Is there a limit in MB to use this plugin?

```

I’m not sure what you mean. Like does the plugin need a certain amount of space to be installed? Or a limit on how large of a site it can export?

```auto
Is that just a copy that I am going to export or its going to really remove the site from where it is and export it?

```

It will just be a copy!

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 5:28pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/8 "2023-08-12T17:28:42Z")

</div>

I mean a limit on how large of a site can export

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 5:30pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/9 "2023-08-12T17:30:25Z")

</div>

In the sceenshot above I can’t see the Database. Can you see the database?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 5:34pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/10 "2023-08-12T17:34:34Z")

</div>

```auto
I mean a limit on how large of a site can export

```

I’m not certain without looking at their documentation. How large is this site? Generally speaking with manual imports it shouldn’t be too much of a concern although it can sometimes take awhile for things to get exported/imported.

```auto
In the sceenshot above I can’t see the Database. Can you see the database?

```

No I do not see the database in your screenshot

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 5:40pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/11 "2023-08-12T17:40:57Z")

</div>

Is the database also supposed to be in the public\_html file or is normally located in a separate file elsewhere?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 6:20pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/12 "2023-08-12T18:20:02Z")

</div>

Where is your site currently hosted that you pulled the backup file from?

Did you download the backup from their interface or did you use some other backup plugin to get the file?

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 7:35pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/13 "2023-08-12T19:35:55Z")

</div>

My website is hosted in hostinger. I used Filezilla to import the files locally.  
Why would we just use plugins while we could just download the files from the host interface?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 7:41pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/14 "2023-08-12T19:41:12Z")

</div>

I was just recommending the plugin as a potential workaround to get a full site export with everything you need together. I’ve never used Hostinger myself, but looking at their documentation it looks like you have the option to download the site files and database separately or together. You could try the latter method to ensure everything you need is included to be able to have a complete import for Local.

> **[How to Download Backups at Hostinger | Hostinger Help Center](https://support.hostinger.com/en/articles/5981435-how-to-download-backups-at-hostinger)**
>
> Downloading your website backups at Hostinger

If you’re pulling all the files manually via FTP, then you could manually import them into Local with some extra steps like this:

- Create a new, blank site in Local. Use whatever username/password you like since you’ll overwrite the DB with this site archive’s dump.
- Copy the wp-content folder from the unzipped location to this newly created site’s location
- Copy the correct SQL dump to the site root. If you still don’t have the SQL, you could use the documentation from Hostinger above to just download the DB.
- Within Local, open the site shell
- Import the dump with `wp db import <dumpfile>`
- If that works, now Search and replace the domains. `wp search-replace ' https://production.com ' 'http:mylocalsite.local'`

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 12, 2023, 8:16pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/15 "2023-08-12T20:16:39Z")

</div>

For these extra steps the wp-content and the sql need to be zipped?

---

<div class="post-metadata">

**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\
**Post date:** [August 12, 2023, 8:21pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/16 "2023-08-12T20:21:11Z")

</div>

No, in the manual steps you would be importing into the blank site manually, replacing the automatically generated files. Again this is just another workaround if you’re not able to get a zip export working for the direct import.

---

<div class="post-metadata">

**Author:** ![Mike4](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Mike4](https://community.localwp.com/u/Mike4)\
**Post date:** [August 14, 2023, 7:46am UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/17 "2023-08-14T07:46:02Z")

</div>

I finally successfully imported the site into local. I used WP Migrate Lite.  
Thank you so much.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 15, 2023, 7:46pm UTC](https://community.localwp.com/t/please-try-again-with-a-to-compatible-zip-file/38555/18 "2023-08-15T19:46:41Z")

</div>

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
